Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5f314e967faf681ce9283377de2d24afbf8f5cf6d88ab54fa4e90cb95d64ddd

Tx prefix hash: 0cd1ed064a4b269addb8ee4b12e564fe43a3424215924c509064c74f04f1b56d
Tx public key: 58d4aea47a01e27000e71a007278c6384180cc3eea5e12b96f344990a157a235
Timestamp: 1588734298 Timestamp [UCT]: 2020-05-06 03:04:58 Age [y:d:h:m:s]: 04:241:07:26:15
Block: 98724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089088 RingCT/type: yes/0
Extra: 0158d4aea47a01e27000e71a007278c6384180cc3eea5e12b96f344990a157a23502110000000186362411000000000000000000

1 output(s) for total of 288.992897596000 dcy

stealth address amount amount idx
00: ee1256555e5e8d9bb022cea5209bb2efdc60bde28d5a0ae922cfb81b789dea1f 288.992897596000 174458 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": 98734, "vin": [ { "gen": { "height": 98724 } } ], "vout": [ { "amount": 288992897596, "target": { "key": "ee1256555e5e8d9bb022cea5209bb2efdc60bde28d5a0ae922cfb81b789dea1f" } } ], "extra": [ 1, 88, 212, 174, 164, 122, 1, 226, 112, 0, 231, 26, 0, 114, 120, 198, 56, 65, 128, 204, 62, 234, 94, 18, 185, 111, 52, 73, 144, 161, 87, 162, 53, 2, 17, 0, 0, 0, 1, 134, 54, 36, 17, 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