Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 419364acfb3d60ba1ba005f40d4e3d67aa9076b84aeaf733120148040e9f0265

Tx prefix hash: 26c087a5aa5878a78de1d715864014e5ab0d63ff2a4cd79a5cc56fb2ff09a9e2
Tx public key: 5f1bcbc1e5cdc708f56bd1d7ce5dd8aa0999e51b3a4aa2dcd6ac42a107689aa3
Timestamp: 1707102414 Timestamp [UCT]: 2024-02-05 03:06:54 Age [y:d:h:m:s]: 00:345:07:18:59
Block: 950612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247203 RingCT/type: yes/0
Extra: 015f1bcbc1e5cdc708f56bd1d7ce5dd8aa0999e51b3a4aa2dcd6ac42a107689aa30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 811170cb0fb3b32b16e7cf75cab05a4034a40285478d49b18a0a6500c9b9ad47 0.600000000000 1409258 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": 950622, "vin": [ { "gen": { "height": 950612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "811170cb0fb3b32b16e7cf75cab05a4034a40285478d49b18a0a6500c9b9ad47" } } ], "extra": [ 1, 95, 27, 203, 193, 229, 205, 199, 8, 245, 107, 209, 215, 206, 93, 216, 170, 9, 153, 229, 27, 58, 74, 162, 220, 214, 172, 66, 161, 7, 104, 154, 163, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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