Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 792ac77530ce5676e048dfe49b97a50afa0cac0d4447e91c1de75303a0da0c61

Tx prefix hash: 51b90c575e7d90bb6fdc6789680efb82728508f7ce56e5f38681f98dbeaaeb7e
Tx public key: fa23f831ef9ee009d666441ae1d8fafe6e96daf46d1d7330b714ae1042d19d0c
Timestamp: 1736937690 Timestamp [UCT]: 2025-01-15 10:41:30 Age [y:d:h:m:s]: 00:061:01:49:24
Block: 1197822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43447 RingCT/type: yes/0
Extra: 01fa23f831ef9ee009d666441ae1d8fafe6e96daf46d1d7330b714ae1042d19d0c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b6000d8cf9ab4dbbf39fc3516fc0b9a11b42acfc680878e84b44ed9e0698fab 0.600000000000 1684439 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": 1197832, "vin": [ { "gen": { "height": 1197822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b6000d8cf9ab4dbbf39fc3516fc0b9a11b42acfc680878e84b44ed9e0698fab" } } ], "extra": [ 1, 250, 35, 248, 49, 239, 158, 224, 9, 214, 102, 68, 26, 225, 216, 250, 254, 110, 150, 218, 244, 109, 29, 115, 48, 183, 20, 174, 16, 66, 209, 157, 12, 2, 17, 0, 0, 0, 1, 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