Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddaec3aed5463ab2c99b7e2e374b67bd24eef6b733df36f030b8b7c8803eda8a

Tx prefix hash: 272de8a4e7888fb929f7626fa6fc1b127ad57783a91cac19f849dc2beb9123b7
Tx public key: 49bc37b2c9e8e5041ebf75f0a56ef439a9e8911efd1eac04a52760bee7e3cf89
Timestamp: 1733569367 Timestamp [UCT]: 2024-12-07 11:02:47 Age [y:d:h:m:s]: 00:196:20:41:09
Block: 1169951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140357 RingCT/type: yes/0
Extra: 0149bc37b2c9e8e5041ebf75f0a56ef439a9e8911efd1eac04a52760bee7e3cf89021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f58abfbd2ebf2132b1b448331a5ab15b2afda239c027a49dd3bd22294f568388 0.600000000000 1655678 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": 1169961, "vin": [ { "gen": { "height": 1169951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f58abfbd2ebf2132b1b448331a5ab15b2afda239c027a49dd3bd22294f568388" } } ], "extra": [ 1, 73, 188, 55, 178, 201, 232, 229, 4, 30, 191, 117, 240, 165, 110, 244, 57, 169, 232, 145, 30, 253, 30, 172, 4, 165, 39, 96, 190, 231, 227, 207, 137, 2, 17, 0, 0, 0, 8, 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