Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4201bbba1586b228ae8cca6960fdae0828c6a48c8a48cc913d0125c18710b0ec

Tx prefix hash: 6cf6d4a0d6d7ef459aa39976bac319d6a51e40e16904d82e753251d9739d2f16
Tx public key: f8227985dc50c2725e317636e731e43bcd9b87cc0b852e0651b7a8c141c2142c
Timestamp: 1709937752 Timestamp [UCT]: 2024-03-08 22:42:32 Age [y:d:h:m:s]: 01:240:06:58:03
Block: 974141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430440 RingCT/type: yes/0
Extra: 01f8227985dc50c2725e317636e731e43bcd9b87cc0b852e0651b7a8c141c2142c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45c208a2b43903480d93540bf9763c2f620be2b66cefd758a1fafadd1ecbe9bb 0.600000000000 1434092 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": 974151, "vin": [ { "gen": { "height": 974141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45c208a2b43903480d93540bf9763c2f620be2b66cefd758a1fafadd1ecbe9bb" } } ], "extra": [ 1, 248, 34, 121, 133, 220, 80, 194, 114, 94, 49, 118, 54, 231, 49, 228, 59, 205, 155, 135, 204, 11, 133, 46, 6, 81, 183, 168, 193, 65, 194, 20, 44, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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