Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1c32f3342fe8048aa9d24fa77536297cbc25a80ae41a7fb9c4858ac0f1bc99d

Tx prefix hash: c0dd709919b720dd6a630f6c9583b6df870fccf18227bf7ad5603624abf3da8c
Tx public key: 10befd74e96c753ade3f340af1f9ff40b39ee1a65ab59f3ba1582f779e642b76
Timestamp: 1578637432 Timestamp [UCT]: 2020-01-10 06:23:52 Age [y:d:h:m:s]: 05:126:03:08:39
Block: 42265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1240388 RingCT/type: yes/0
Extra: 0110befd74e96c753ade3f340af1f9ff40b39ee1a65ab59f3ba1582f779e642b76021100000029b221b3d1000000000000000000

1 output(s) for total of 444.589656273000 dcy

stealth address amount amount idx
00: 44154775ef45a178b53b6425564ec62eeb164a009ddac4a1c4947dc5e5f34fa5 444.589656273000 76071 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": 42275, "vin": [ { "gen": { "height": 42265 } } ], "vout": [ { "amount": 444589656273, "target": { "key": "44154775ef45a178b53b6425564ec62eeb164a009ddac4a1c4947dc5e5f34fa5" } } ], "extra": [ 1, 16, 190, 253, 116, 233, 108, 117, 58, 222, 63, 52, 10, 241, 249, 255, 64, 179, 158, 225, 166, 90, 181, 159, 59, 161, 88, 47, 119, 158, 100, 43, 118, 2, 17, 0, 0, 0, 41, 178, 33, 179, 209, 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