Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee5e42ef42a95355661816401b4305d6ce035c425f1c35370ca842396cdd9cd

Tx prefix hash: 275eacae7a336365bf0ccf2be7b7dd3b4df6ce771a6cc1e250c4057e4a468d6b
Tx public key: f09a9407170f53e5a6fc427894f0fc31af34a878569c7d16e660048cb3cb4fe4
Timestamp: 1737162969 Timestamp [UCT]: 2025-01-18 01:16:09 Age [y:d:h:m:s]: 00:155:01:43:08
Block: 1199693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110471 RingCT/type: yes/0
Extra: 01f09a9407170f53e5a6fc427894f0fc31af34a878569c7d16e660048cb3cb4fe4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1da0c5a75c6f44e2be4aa35c58ff579519a6b3f307141b233292a2415008d77 0.600000000000 1686326 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": 1199703, "vin": [ { "gen": { "height": 1199693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1da0c5a75c6f44e2be4aa35c58ff579519a6b3f307141b233292a2415008d77" } } ], "extra": [ 1, 240, 154, 148, 7, 23, 15, 83, 229, 166, 252, 66, 120, 148, 240, 252, 49, 175, 52, 168, 120, 86, 156, 125, 22, 230, 96, 4, 140, 179, 203, 79, 228, 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