Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff659374606c7c0d3e41e6fd05310dc91469296724ad05ce1c8e5b1e5c0eacdd

Tx prefix hash: 4c0545f7f1c4c3933dbe867fd2b28fbe668e53ccd616b902f10a7eae47c22def
Tx public key: 6df97dcedc4e417bfcafee2bbe64a7a3c094805d154c9a08de1ec008d355bb58
Timestamp: 1699035895 Timestamp [UCT]: 2023-11-03 18:24:55 Age [y:d:h:m:s]: 01:139:16:27:09
Block: 883957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360826 RingCT/type: yes/0
Extra: 016df97dcedc4e417bfcafee2bbe64a7a3c094805d154c9a08de1ec008d355bb5802110000000a33af99f4000000000000000000

1 output(s) for total of 0.722908811000 dcy

stealth address amount amount idx
00: f40da10ec393bd8e002004617347190c6de3691505bbbc715bdb9fc41410d5d5 0.722908811000 1339686 of 0

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": 883967, "vin": [ { "gen": { "height": 883957 } } ], "vout": [ { "amount": 722908811, "target": { "key": "f40da10ec393bd8e002004617347190c6de3691505bbbc715bdb9fc41410d5d5" } } ], "extra": [ 1, 109, 249, 125, 206, 220, 78, 65, 123, 252, 175, 238, 43, 190, 100, 167, 163, 192, 148, 128, 93, 21, 76, 154, 8, 222, 30, 192, 8, 211, 85, 187, 88, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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