Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe8a1b1f85977fb458a378cab38404d3692737d3b3db76b46ea7709857fe565a

Tx prefix hash: 236495a0467fc7138fce00b390c1e8a2b5cf0f6f2e5cd8ea8cdf175acf110d17
Tx public key: 7c480918ab74532147141c632d187147c0fa698095f2b2efd09ef08059fcd7c3
Timestamp: 1724173354 Timestamp [UCT]: 2024-08-20 17:02:34 Age [y:d:h:m:s]: 00:298:05:45:17
Block: 1092162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212974 RingCT/type: yes/0
Extra: 017c480918ab74532147141c632d187147c0fa698095f2b2efd09ef08059fcd7c3021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1f2a0749832d4b841a45c5a8270dfb860b6322553f0dcb1e9f16d619e5eda75 0.600000000000 1566853 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": 1092172, "vin": [ { "gen": { "height": 1092162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1f2a0749832d4b841a45c5a8270dfb860b6322553f0dcb1e9f16d619e5eda75" } } ], "extra": [ 1, 124, 72, 9, 24, 171, 116, 83, 33, 71, 20, 28, 99, 45, 24, 113, 71, 192, 250, 105, 128, 149, 242, 178, 239, 208, 158, 240, 128, 89, 252, 215, 195, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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