Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9be899c7d6490e46b428e230838e0d89cf3c4fd2fe85c5bd9a433ac3fa9ec0f7

Tx prefix hash: b258ba8268c8a073d4de7cfe37930e1cabdaa18ff79e335507ee309fff80a1e0
Tx public key: 293c89d430b6cd09f3902d663c509b993b32cdbf1ffe3665965980d7a728d39e
Timestamp: 1718974641 Timestamp [UCT]: 2024-06-21 12:57:21 Age [y:d:h:m:s]: 00:328:03:31:59
Block: 1049025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234544 RingCT/type: yes/0
Extra: 01293c89d430b6cd09f3902d663c509b993b32cdbf1ffe3665965980d7a728d39e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7056109964bf2e95b39afbd0dbea3948089da4200b48a47a14ee98e7d7f49a5 0.600000000000 1519122 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": 1049035, "vin": [ { "gen": { "height": 1049025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7056109964bf2e95b39afbd0dbea3948089da4200b48a47a14ee98e7d7f49a5" } } ], "extra": [ 1, 41, 60, 137, 212, 48, 182, 205, 9, 243, 144, 45, 102, 60, 80, 155, 153, 59, 50, 205, 191, 31, 254, 54, 101, 150, 89, 128, 215, 167, 40, 211, 158, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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