Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0b6545cdcbc253b3f185dcc5dc166d90dbed8caf5b3ce3ccfad4aecdce18f27

Tx prefix hash: 479814fe921604c2ace2d1fe07cbf6bdd07a273e44f68970ee883dfd7000abb1
Tx public key: 6fc8a0afd4cc7837761fef42c62a8b2417a1edbd315cc62c9683f42dc02d2010
Timestamp: 1718265722 Timestamp [UCT]: 2024-06-13 08:02:02 Age [y:d:h:m:s]: 00:287:19:05:38
Block: 1043181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205653 RingCT/type: yes/0
Extra: 016fc8a0afd4cc7837761fef42c62a8b2417a1edbd315cc62c9683f42dc02d20100211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c4d30d144c3e2dfddc19e06fece70b64a73f80c24e3ce293d46309b07c86e3b 0.600000000000 1512274 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": 1043191, "vin": [ { "gen": { "height": 1043181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c4d30d144c3e2dfddc19e06fece70b64a73f80c24e3ce293d46309b07c86e3b" } } ], "extra": [ 1, 111, 200, 160, 175, 212, 204, 120, 55, 118, 31, 239, 66, 198, 42, 139, 36, 23, 161, 237, 189, 49, 92, 198, 44, 150, 131, 244, 45, 192, 45, 32, 16, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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