Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9593ccdcfb7c14481af7ebe8b97a7c382aa3a743c60e0badbff0f6d91d3822a

Tx prefix hash: cd1465dfa65a1743fff5f58585b43f81057ea8fbe9de64333d6936bbdebab54b
Tx public key: 346d78158867cf47e6b351a4d178b6b325cdf870a1803c66cfa605c584e9ed9a
Timestamp: 1732602530 Timestamp [UCT]: 2024-11-26 06:28:50 Age [y:d:h:m:s]: 00:135:14:09:55
Block: 1161937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96717 RingCT/type: yes/0
Extra: 01346d78158867cf47e6b351a4d178b6b325cdf870a1803c66cfa605c584e9ed9a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bec6ee6178564c06bd0c3910e60c94e2b84ab6572a008275fe7b2ddce5a21cf6 0.600000000000 1647592 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": 1161947, "vin": [ { "gen": { "height": 1161937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bec6ee6178564c06bd0c3910e60c94e2b84ab6572a008275fe7b2ddce5a21cf6" } } ], "extra": [ 1, 52, 109, 120, 21, 136, 103, 207, 71, 230, 179, 81, 164, 209, 120, 182, 179, 37, 205, 248, 112, 161, 128, 60, 102, 207, 166, 5, 197, 132, 233, 237, 154, 2, 17, 0, 0, 0, 3, 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