Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a80a33583edf90a21f42abc9c95bd2a7f1d706f5e418bd800ea365150c60414

Tx prefix hash: 32f00a0f8200bc73171a54a66ee45c148e0b882fb8f7d0379cc805f0ffdfbb18
Tx public key: 4859c86bf0e3594476def63f9cbacdfbf1e02c21c62b2da015ae496b3d14b878
Timestamp: 1720107638 Timestamp [UCT]: 2024-07-04 15:40:38 Age [y:d:h:m:s]: 00:263:04:41:17
Block: 1058441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188043 RingCT/type: yes/0
Extra: 014859c86bf0e3594476def63f9cbacdfbf1e02c21c62b2da015ae496b3d14b8780211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 428e9f7fbb3af62a1db795959354af84c15e9f95e8402d8023a3e679922278ee 0.600000000000 1528896 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": 1058451, "vin": [ { "gen": { "height": 1058441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "428e9f7fbb3af62a1db795959354af84c15e9f95e8402d8023a3e679922278ee" } } ], "extra": [ 1, 72, 89, 200, 107, 240, 227, 89, 68, 118, 222, 246, 63, 156, 186, 205, 251, 241, 224, 44, 33, 198, 43, 45, 160, 21, 174, 73, 107, 61, 20, 184, 120, 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