Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7004717a17f37dbd7b2b632240ebb03d69e69a1608d9579eaecbd519c9df7c4a

Tx prefix hash: 5596c1ad8df4da3d2273dd10be824847626d272e0ad5b82addea756cc0bf9fe7
Tx public key: 1d9b396e84e181e2e0de0b44fd218573fd17c9f523fd267c4399462e3e86a9e8
Timestamp: 1735910336 Timestamp [UCT]: 2025-01-03 13:18:56 Age [y:d:h:m:s]: 00:165:04:57:28
Block: 1189337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117776 RingCT/type: yes/0
Extra: 011d9b396e84e181e2e0de0b44fd218573fd17c9f523fd267c4399462e3e86a9e8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1722db207c7569eceec3ad6523b7f5cbd66ffbceffd2761415dc858949c797c5 0.600000000000 1675846 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": 1189347, "vin": [ { "gen": { "height": 1189337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1722db207c7569eceec3ad6523b7f5cbd66ffbceffd2761415dc858949c797c5" } } ], "extra": [ 1, 29, 155, 57, 110, 132, 225, 129, 226, 224, 222, 11, 68, 253, 33, 133, 115, 253, 23, 201, 245, 35, 253, 38, 124, 67, 153, 70, 46, 62, 134, 169, 232, 2, 17, 0, 0, 0, 3, 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