Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbc1f7677bccf2e989c1af67775202b5abd4254b3b2ded0f7827323722fa6fcc

Tx prefix hash: dbaa4c96738d3b05577f7aee0bae84a6078bef1de947b26f87605630867f31b7
Tx public key: 17012786adc99290a49a74f31f9d7e244a9f8b670f8508f4764a75bff629dc87
Timestamp: 1734409956 Timestamp [UCT]: 2024-12-17 04:32:36 Age [y:d:h:m:s]: 00:106:17:52:39
Block: 1176931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76049 RingCT/type: yes/0
Extra: 0117012786adc99290a49a74f31f9d7e244a9f8b670f8508f4764a75bff629dc87021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d0aa7e9a6a6435a243af1f3210197357cf14af46a6c361228b34327ddd6bfb5 0.600000000000 1663292 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": 1176941, "vin": [ { "gen": { "height": 1176931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d0aa7e9a6a6435a243af1f3210197357cf14af46a6c361228b34327ddd6bfb5" } } ], "extra": [ 1, 23, 1, 39, 134, 173, 201, 146, 144, 164, 154, 116, 243, 31, 157, 126, 36, 74, 159, 139, 103, 15, 133, 8, 244, 118, 74, 117, 191, 246, 41, 220, 135, 2, 17, 0, 0, 0, 4, 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