Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34c0ad8061ff30520e9dc6e7b77cf2168bdabc7e92364480b5f34f7b4cee7ef5

Tx prefix hash: 84a32682bfdf83afcd8eabc157d68c32c8f20bcc4bff568e725bd1cc2e0f3d49
Tx public key: e3e8b8ad63ec244de691df12f37ca556cfdb21f26a1016cfd1a920ba6452071b
Timestamp: 1731828784 Timestamp [UCT]: 2024-11-17 07:33:04 Age [y:d:h:m:s]: 01:017:20:53:20
Block: 1155520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271231 RingCT/type: yes/0
Extra: 01e3e8b8ad63ec244de691df12f37ca556cfdb21f26a1016cfd1a920ba6452071b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c5b1c272ed1e70e132cf0198839a56bf373c6b44889064d5f75e722f827de6c 0.600000000000 1641137 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": 1155530, "vin": [ { "gen": { "height": 1155520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c5b1c272ed1e70e132cf0198839a56bf373c6b44889064d5f75e722f827de6c" } } ], "extra": [ 1, 227, 232, 184, 173, 99, 236, 36, 77, 230, 145, 223, 18, 243, 124, 165, 86, 207, 219, 33, 242, 106, 16, 22, 207, 209, 169, 32, 186, 100, 82, 7, 27, 2, 17, 0, 0, 0, 2, 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