Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52b274424ed7f5f755b13d1a6421c3a57f64e3ddb36428acf570975156fc3f57

Tx prefix hash: fd8bbfc14bbf6dd5b33cd6848cdcdbf160fe21f3466fc597a16e2cef869152ea
Tx public key: efad3b2171ca1b298cb75efb63ee4ccd15b7c9a6b523e0a81b1ce6a6156e06a0
Timestamp: 1579098948 Timestamp [UCT]: 2020-01-15 14:35:48 Age [y:d:h:m:s]: 05:109:03:39:45
Block: 46146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228182 RingCT/type: yes/0
Extra: 01efad3b2171ca1b298cb75efb63ee4ccd15b7c9a6b523e0a81b1ce6a6156e06a002110000009fb221b3d1000000000000000000

1 output(s) for total of 439.083083816000 dcy

stealth address amount amount idx
00: 119a0c3c0e45010818dc15a7c64f31ddded4a07f39908dee508c18c920789f1b 439.083083816000 84729 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": 46156, "vin": [ { "gen": { "height": 46146 } } ], "vout": [ { "amount": 439083083816, "target": { "key": "119a0c3c0e45010818dc15a7c64f31ddded4a07f39908dee508c18c920789f1b" } } ], "extra": [ 1, 239, 173, 59, 33, 113, 202, 27, 41, 140, 183, 94, 251, 99, 238, 76, 205, 21, 183, 201, 166, 181, 35, 224, 168, 27, 28, 230, 166, 21, 110, 6, 160, 2, 17, 0, 0, 0, 159, 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