Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf2184b89321dfda882e95c61ef2448339fc5e11f2336e17a0883f75cd8b071a

Tx prefix hash: 9ef24876ec8018e9efd01a1cb3221f0d250077f9b7e4c37cf5c0d8cb39952df6
Tx public key: 51076ddbc7f0b6b3141e7ca46dbed8200c4218805da1aff59ec4dff8a3cd53ec
Timestamp: 1729492700 Timestamp [UCT]: 2024-10-21 06:38:20 Age [y:d:h:m:s]: 00:001:14:52:51
Block: 1136216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1165 RingCT/type: yes/0
Extra: 0151076ddbc7f0b6b3141e7ca46dbed8200c4218805da1aff59ec4dff8a3cd53ec021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17b93f07ea42fa4f52c58fd060b8c7df2c80984edb8c2659683b967f46e7dea1 0.600000000000 1619559 of 15

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": 1136226, "vin": [ { "gen": { "height": 1136216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17b93f07ea42fa4f52c58fd060b8c7df2c80984edb8c2659683b967f46e7dea1" } } ], "extra": [ 1, 81, 7, 109, 219, 199, 240, 182, 179, 20, 30, 124, 164, 109, 190, 216, 32, 12, 66, 24, 128, 93, 161, 175, 245, 158, 196, 223, 248, 163, 205, 83, 236, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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