Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 491d85c6da6e5154c7a365c08995cc6c49f31cd62f89ccbb69210a872392a501

Tx prefix hash: 2bd04118bbf4ffc092be95619d8b63936d2b96f02413b0dc237dd43b884858a8
Tx public key: 72dbb94f3d7e44ab79310521b45c14f1c774f1f696cc3a4fab0380326b3a7bd2
Timestamp: 1732482158 Timestamp [UCT]: 2024-11-24 21:02:38 Age [y:d:h:m:s]: 00:121:08:21:38
Block: 1160943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86518 RingCT/type: yes/0
Extra: 0172dbb94f3d7e44ab79310521b45c14f1c774f1f696cc3a4fab0380326b3a7bd2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4119a366d4e00e2254a47d6dd2f0692c5f57cdb17afd80d156ee2c572d47696a 0.600000000000 1646594 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": 1160953, "vin": [ { "gen": { "height": 1160943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4119a366d4e00e2254a47d6dd2f0692c5f57cdb17afd80d156ee2c572d47696a" } } ], "extra": [ 1, 114, 219, 185, 79, 61, 126, 68, 171, 121, 49, 5, 33, 180, 92, 20, 241, 199, 116, 241, 246, 150, 204, 58, 79, 171, 3, 128, 50, 107, 58, 123, 210, 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