Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9459dca01190ff14eec569ca2b9021194bb1d31d3ae7c200775ee973a9a0450

Tx prefix hash: 23212b74a7f38c84e61f348f43c9bec6533b0d11fe1a598246ef46c8d41b47a9
Tx public key: 9bf5dc6bf0c2e1ae76079f87262c550934231ed992d851ee64169ce68c9ee59b
Timestamp: 1720787522 Timestamp [UCT]: 2024-07-12 12:32:02 Age [y:d:h:m:s]: 00:248:15:04:18
Block: 1064094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177616 RingCT/type: yes/0
Extra: 019bf5dc6bf0c2e1ae76079f87262c550934231ed992d851ee64169ce68c9ee59b02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d63ae2e723006ad14270bef1284f48db95808e01c7c9c98ced4b8aa167872e8 0.600000000000 1534617 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": 1064104, "vin": [ { "gen": { "height": 1064094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d63ae2e723006ad14270bef1284f48db95808e01c7c9c98ced4b8aa167872e8" } } ], "extra": [ 1, 155, 245, 220, 107, 240, 194, 225, 174, 118, 7, 159, 135, 38, 44, 85, 9, 52, 35, 30, 217, 146, 216, 81, 238, 100, 22, 156, 230, 140, 158, 229, 155, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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