Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 091b7b278928148b269af6fedc961c16b323ed8e2ff77ba774e0325bf7cf4685

Tx prefix hash: 439a7ff622f34d278468da15c98881aef9dbe90a829e168347a0e6518f66e09d
Tx public key: beaf237f4cb8fd216d1d31388495b564563bb7b8b5e4c2acb47c82950e9e43d6
Timestamp: 1575768575 Timestamp [UCT]: 2019-12-08 01:29:35 Age [y:d:h:m:s]: 05:061:18:20:37
Block: 22913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1189935 RingCT/type: yes/0
Extra: 01beaf237f4cb8fd216d1d31388495b564563bb7b8b5e4c2acb47c82950e9e43d6020d3930303100030000000790824d

1 output(s) for total of 515.324264436000 dcy

stealth address amount amount idx
00: eb4875b5f4009f5cf29674b31f27693a0b537d2a73c49c7d8c4b1f1e7554d90b 515.324264436000 36312 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": 22923, "vin": [ { "gen": { "height": 22913 } } ], "vout": [ { "amount": 515324264436, "target": { "key": "eb4875b5f4009f5cf29674b31f27693a0b537d2a73c49c7d8c4b1f1e7554d90b" } } ], "extra": [ 1, 190, 175, 35, 127, 76, 184, 253, 33, 109, 29, 49, 56, 132, 149, 181, 100, 86, 59, 183, 184, 181, 228, 194, 172, 180, 124, 130, 149, 14, 158, 67, 214, 2, 13, 57, 48, 48, 49, 0, 3, 0, 0, 0, 7, 144, 130, 77 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8