Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 797449be71e3dee82c78d009308c5085eba61f6daf5cf7073fadf6d808681811

Tx prefix hash: c94c56191ab2f976e12d1746a008cdf7dfcb7d1d15bc6e28d8aa5a3caa446532
Tx public key: 6863fe77c578ea80c151a952ddd0491df4e2f4f1f824b038c363646d1f8cca91
Timestamp: 1713542655 Timestamp [UCT]: 2024-04-19 16:04:15 Age [y:d:h:m:s]: 00:209:10:35:47
Block: 1004016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149923 RingCT/type: yes/0
Extra: 016863fe77c578ea80c151a952ddd0491df4e2f4f1f824b038c363646d1f8cca910211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc36da77617ecd28473fadd7386fea28211f39cdfa82d35b8c818dcdae304603 0.600000000000 1464576 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": 1004026, "vin": [ { "gen": { "height": 1004016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc36da77617ecd28473fadd7386fea28211f39cdfa82d35b8c818dcdae304603" } } ], "extra": [ 1, 104, 99, 254, 119, 197, 120, 234, 128, 193, 81, 169, 82, 221, 208, 73, 29, 244, 226, 244, 241, 248, 36, 176, 56, 195, 99, 100, 109, 31, 140, 202, 145, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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