Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbae2792519286be474992f08a2f534eb7da16f4dfde662e3496d2fbd63eed5e

Tx prefix hash: cd7f9d83a66f3c917561e6b4a9ea7fd66ee4b3dde72dce98eba812f18d77ec1e
Tx public key: 2cf980126a85d35863628b07c91eef8adaa12109951ffcabcc4e6ecc9a0a3ebc
Timestamp: 1704889599 Timestamp [UCT]: 2024-01-10 12:26:39 Age [y:d:h:m:s]: 01:005:16:41:27
Block: 932275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265383 RingCT/type: yes/0
Extra: 012cf980126a85d35863628b07c91eef8adaa12109951ffcabcc4e6ecc9a0a3ebc0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0c1ac23caa94b60562d69cf462894bafad4b2b21d4d4ae30ccec3700d8d220f 0.600000000000 1390205 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": 932285, "vin": [ { "gen": { "height": 932275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0c1ac23caa94b60562d69cf462894bafad4b2b21d4d4ae30ccec3700d8d220f" } } ], "extra": [ 1, 44, 249, 128, 18, 106, 133, 211, 88, 99, 98, 139, 7, 201, 30, 239, 138, 218, 161, 33, 9, 149, 31, 252, 171, 204, 78, 110, 204, 154, 10, 62, 188, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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