Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eda1d6cd42a2379abc63f11db632656b36d88b816cb68662d1acb3ad70daa0d2

Tx prefix hash: e9e6715debb6a8d0e9aa24842b746fc1a3e88f0c35a3f13e5fd81f1c9ede8401
Tx public key: e1e6e2abf73ea16346c8c58c2031a0aac98f67cc0d309c08beb1d15ce5c87241
Timestamp: 1707143642 Timestamp [UCT]: 2024-02-05 14:34:02 Age [y:d:h:m:s]: 01:060:09:55:54
Block: 950955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304238 RingCT/type: yes/0
Extra: 01e1e6e2abf73ea16346c8c58c2031a0aac98f67cc0d309c08beb1d15ce5c8724102110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ab956c26e5658d0d7100e354cc2c912196a0839dcf171c4e035a29bba954ddb 0.600000000000 1409653 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": 950965, "vin": [ { "gen": { "height": 950955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ab956c26e5658d0d7100e354cc2c912196a0839dcf171c4e035a29bba954ddb" } } ], "extra": [ 1, 225, 230, 226, 171, 247, 62, 161, 99, 70, 200, 197, 140, 32, 49, 160, 170, 201, 143, 103, 204, 13, 48, 156, 8, 190, 177, 209, 92, 229, 200, 114, 65, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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