Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 75f909907cfe0f0913a1e3e3c847620541c0273e2fef54bd55c5f5bc95b8ce1c

Tx prefix hash: 8550a92ee88ab7a88a7153622dba07fd7f07d7011bcf77946842e4c06c2c65e0
Tx public key: f52af9c8cd5d96fb0c6a33c651bf679e09e96bf65e5c3be2b844bc0aa8458662
Timestamp: 1729877778 Timestamp [UCT]: 2024-10-25 17:36:18 Age [y:d:h:m:s]: 00:147:12:34:37
Block: 1139410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105235 RingCT/type: yes/0
Extra: 01f52af9c8cd5d96fb0c6a33c651bf679e09e96bf65e5c3be2b844bc0aa8458662021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7fd5faf888fafab5b6e0784435b7730ccbcfb842fad76f3406a22b711ef3112 0.600000000000 1623197 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1139420, "vin": [ { "gen": { "height": 1139410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7fd5faf888fafab5b6e0784435b7730ccbcfb842fad76f3406a22b711ef3112" } } ], "extra": [ 1, 245, 42, 249, 200, 205, 93, 150, 251, 12, 106, 51, 198, 81, 191, 103, 158, 9, 233, 107, 246, 94, 92, 59, 226, 184, 68, 188, 10, 168, 69, 134, 98, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8