Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78bab088f242e3e2938d86026d8e0f320f92328378d1ef0bd74f1e5456bc442d

Tx prefix hash: d6cd0b3f55393ed83cceda2411641c0676037f0218cc51534543b5cd70e9b34b
Tx public key: 9f59a22c3a1e84e57fa338ee285d44d6c0e60622baa44a0c8574a3968d8be082
Timestamp: 1701282356 Timestamp [UCT]: 2023-11-29 18:25:56 Age [y:d:h:m:s]: 01:181:12:30:24
Block: 902371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390953 RingCT/type: yes/0
Extra: 019f59a22c3a1e84e57fa338ee285d44d6c0e60622baa44a0c8574a3968d8be08202110000000dfaf35c9c000000000000000000

1 output(s) for total of 0.628159981000 dcy

stealth address amount amount idx
00: fa46a8dccfd43c06617a1c12804379587ceb4589069e7320c9d329676916ca55 0.628159981000 1359010 of 0

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": 902381, "vin": [ { "gen": { "height": 902371 } } ], "vout": [ { "amount": 628159981, "target": { "key": "fa46a8dccfd43c06617a1c12804379587ceb4589069e7320c9d329676916ca55" } } ], "extra": [ 1, 159, 89, 162, 44, 58, 30, 132, 229, 127, 163, 56, 238, 40, 93, 68, 214, 192, 230, 6, 34, 186, 164, 74, 12, 133, 116, 163, 150, 141, 139, 224, 130, 2, 17, 0, 0, 0, 13, 250, 243, 92, 156, 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