Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b72e4966d8783711cf7b751be82ae0e533aadcf4db1e94df2e5184de957cfa5b

Tx prefix hash: 78c3466cea58caeb1165c4e8fb610a6d5d69a3455fd96d413f45ce7e2577e763
Tx public key: f3dfc319d9584948fbfbe54a4794e31648024f96db433ce3ba49551e445707cb
Timestamp: 1574567820 Timestamp [UCT]: 2019-11-24 03:57:00 Age [y:d:h:m:s]: 05:145:09:56:18
Block: 16145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1246610 RingCT/type: yes/0
Extra: 01f3dfc319d9584948fbfbe54a4794e31648024f96db433ce3ba49551e445707cb021100000008f95225a5000000000000000000

1 output(s) for total of 542.632492349000 dcy

stealth address amount amount idx
00: 4ae5b11ee32b1978169429c2d877a152518c397de49d0b3c74d0e99f3a5713da 542.632492349000 22359 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": 16155, "vin": [ { "gen": { "height": 16145 } } ], "vout": [ { "amount": 542632492349, "target": { "key": "4ae5b11ee32b1978169429c2d877a152518c397de49d0b3c74d0e99f3a5713da" } } ], "extra": [ 1, 243, 223, 195, 25, 217, 88, 73, 72, 251, 251, 229, 74, 71, 148, 227, 22, 72, 2, 79, 150, 219, 67, 60, 227, 186, 73, 85, 30, 68, 87, 7, 203, 2, 17, 0, 0, 0, 8, 249, 82, 37, 165, 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