Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d76d91e14b8732313ce103497d9fe8fb87eb69b0977a7d151acb3e3d7faa697a

Tx prefix hash: 004f52d547fd9733580139170bff5cb28a9f6946ef4190f0a8cd53873d901257
Tx public key: 288198353f174576f13dfadc016cc4537d9f13c3df3364dd0d1c8a5abb1d2464
Timestamp: 1647090062 Timestamp [UCT]: 2022-03-12 13:01:02 Age [y:d:h:m:s]: 02:260:19:25:04
Block: 456831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705887 RingCT/type: yes/0
Extra: 01288198353f174576f13dfadc016cc4537d9f13c3df3364dd0d1c8a5abb1d24640211000000165eb576c5000000000000000000

1 output(s) for total of 18.807433123000 dcy

stealth address amount amount idx
00: 7da771f22ea9e8b70fdce368357d7269eae2dada9a25822f58ea6ca3ca2818c8 18.807433123000 872968 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": 456841, "vin": [ { "gen": { "height": 456831 } } ], "vout": [ { "amount": 18807433123, "target": { "key": "7da771f22ea9e8b70fdce368357d7269eae2dada9a25822f58ea6ca3ca2818c8" } } ], "extra": [ 1, 40, 129, 152, 53, 63, 23, 69, 118, 241, 61, 250, 220, 1, 108, 196, 83, 125, 159, 19, 195, 223, 51, 100, 221, 13, 28, 138, 90, 187, 29, 36, 100, 2, 17, 0, 0, 0, 22, 94, 181, 118, 197, 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