Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbc118ac28eef3f587c9d61f2fc27676703684a57eaa1ecf6e61cc1e62b4687e

Tx prefix hash: 090806c6151fff3f27434a0be72efe48ade577c51e5434153e142a09aa355e54
Tx public key: 31545db61ed4e3c2ffe208b307a42b1b450f695ea69f7d78f9f1f8bb6f89d274
Timestamp: 1728310761 Timestamp [UCT]: 2024-10-07 14:19:21 Age [y:d:h:m:s]: 00:250:16:23:05
Block: 1126459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178906 RingCT/type: yes/0
Extra: 0131545db61ed4e3c2ffe208b307a42b1b450f695ea69f7d78f9f1f8bb6f89d27402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7111ea8f4787034d160e8c6e007e132fd59ae00fe4550ea865f55d9823abf6f1 0.600000000000 1609252 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": 1126469, "vin": [ { "gen": { "height": 1126459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7111ea8f4787034d160e8c6e007e132fd59ae00fe4550ea865f55d9823abf6f1" } } ], "extra": [ 1, 49, 84, 93, 182, 30, 212, 227, 194, 255, 226, 8, 179, 7, 164, 43, 27, 69, 15, 105, 94, 166, 159, 125, 120, 249, 241, 248, 187, 111, 137, 210, 116, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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