Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ba32a38a1bc4303aa17b26444d4687f9fe2f4dfbd175ab38a269cf58237337c

Tx prefix hash: 084cfc19a5c4730333903729dd01e2a245373cbc0c11dec170f0db7561fb5ef3
Tx public key: 963af1b25cec98fe0401f0510b1b32a1d4a073fa3f3abf313e5131ff84cc40e5
Timestamp: 1722209443 Timestamp [UCT]: 2024-07-28 23:30:43 Age [y:d:h:m:s]: 00:246:12:12:48
Block: 1075861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176087 RingCT/type: yes/0
Extra: 01963af1b25cec98fe0401f0510b1b32a1d4a073fa3f3abf313e5131ff84cc40e502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b407fb50db7654d6d8b0ac2484ccd486141e15bb474881f1986dfe73e00539ba 0.600000000000 1548392 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": 1075871, "vin": [ { "gen": { "height": 1075861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b407fb50db7654d6d8b0ac2484ccd486141e15bb474881f1986dfe73e00539ba" } } ], "extra": [ 1, 150, 58, 241, 178, 92, 236, 152, 254, 4, 1, 240, 81, 11, 27, 50, 161, 212, 160, 115, 250, 63, 58, 191, 49, 62, 81, 49, 255, 132, 204, 64, 229, 2, 17, 0, 0, 0, 5, 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