Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 358afda7046bb6a089a840611f25cbd60b8d6f079c45447096a42723eba633af

Tx prefix hash: 21a621cc7de8137e6b23c9cf6bfd0cc87cf24cc2f873bf332b850c4bbf509106
Tx public key: a5706edbdedb47b0f073e91568377c3bec0286cf29592e3343eb21ac40dbc59e
Timestamp: 1578484064 Timestamp [UCT]: 2020-01-08 11:47:44 Age [y:d:h:m:s]: 05:100:23:50:26
Block: 41193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1222202 RingCT/type: yes/0
Extra: 01a5706edbdedb47b0f073e91568377c3bec0286cf29592e3343eb21ac40dbc59e0211000000078a2ee0d9000000000000000000

1 output(s) for total of 448.240750756000 dcy

stealth address amount amount idx
00: b092e02f292e5ee432e8d8f76e59f02921d72f4ee87e84dcbb89ead404d2582b 448.240750756000 73143 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": 41203, "vin": [ { "gen": { "height": 41193 } } ], "vout": [ { "amount": 448240750756, "target": { "key": "b092e02f292e5ee432e8d8f76e59f02921d72f4ee87e84dcbb89ead404d2582b" } } ], "extra": [ 1, 165, 112, 110, 219, 222, 219, 71, 176, 240, 115, 233, 21, 104, 55, 124, 59, 236, 2, 134, 207, 41, 89, 46, 51, 67, 235, 33, 172, 64, 219, 197, 158, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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