Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec4d2a3fa7649bf4124803b1b464cf790d0c42e7a0ad6bac6a99c78118b9632

Tx prefix hash: 971d6696dd585f826288b2feb12be0c934e00ec4df5080e87d6b4e715374fc18
Tx public key: f9da1ac9d8774370a65fa52faf7ee1c412d99eeb3356e4ce6b7204a00574f21c
Timestamp: 1712481287 Timestamp [UCT]: 2024-04-07 09:14:47 Age [y:d:h:m:s]: 01:036:03:22:45
Block: 995199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286822 RingCT/type: yes/0
Extra: 01f9da1ac9d8774370a65fa52faf7ee1c412d99eeb3356e4ce6b7204a00574f21c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e34525cf04ae80be326b1dcadc18a588270ee57db5a29ebf9b0ad134859fd2b 0.600000000000 1455605 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": 995209, "vin": [ { "gen": { "height": 995199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e34525cf04ae80be326b1dcadc18a588270ee57db5a29ebf9b0ad134859fd2b" } } ], "extra": [ 1, 249, 218, 26, 201, 216, 119, 67, 112, 166, 95, 165, 47, 175, 126, 225, 196, 18, 217, 158, 235, 51, 86, 228, 206, 107, 114, 4, 160, 5, 116, 242, 28, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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