Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a6052b06fd3fb4744cf6787479675185ab56e4f0cac2b55e8c6305159cb8c6f

Tx prefix hash: 591f98d251ee88f88cf5bc3a664ea848bc3621d032fef90223309b7960be92df
Tx public key: 5e9fbb20d129f84406d9488db6b087d625885817e513e136732b568a84318eb3
Timestamp: 1613136935 Timestamp [UCT]: 2021-02-12 13:35:35 Age [y:d:h:m:s]: 03:356:22:14:11
Block: 197329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1013855 RingCT/type: yes/0
Extra: 015e9fbb20d129f84406d9488db6b087d625885817e513e136732b568a84318eb30211000002814ea414e5000000000000000000

1 output(s) for total of 136.201760644000 dcy

stealth address amount amount idx
00: 1ebe151e4a8efb1e13533395fad01c7dae2ca0589c0b42ebf19f69de309183e2 136.201760644000 403419 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": 197339, "vin": [ { "gen": { "height": 197329 } } ], "vout": [ { "amount": 136201760644, "target": { "key": "1ebe151e4a8efb1e13533395fad01c7dae2ca0589c0b42ebf19f69de309183e2" } } ], "extra": [ 1, 94, 159, 187, 32, 209, 41, 248, 68, 6, 217, 72, 141, 182, 176, 135, 214, 37, 136, 88, 23, 229, 19, 225, 54, 115, 43, 86, 138, 132, 49, 142, 179, 2, 17, 0, 0, 2, 129, 78, 164, 20, 229, 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