Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e27f99c6c84b4df6e9f2c5a0a783a004b091035a317b1db1fa9e88208914ecc

Tx prefix hash: 9b96f28135d4c0f3be346de799ae2990c8e3141b8d94156c77642d5a530a7c20
Tx public key: d567c325b2ba467d0dd54287c790772ed82fa1bcd9b5518272e5bdb03e14fa37
Timestamp: 1717624616 Timestamp [UCT]: 2024-06-05 21:56:56 Age [y:d:h:m:s]: 00:337:01:28:27
Block: 1037856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240907 RingCT/type: yes/0
Extra: 01d567c325b2ba467d0dd54287c790772ed82fa1bcd9b5518272e5bdb03e14fa370211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67aa75d7ce60e6c562338102b53ad80c252c11ab601a1eed67e6250d89bcfd84 0.600000000000 1506413 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": 1037866, "vin": [ { "gen": { "height": 1037856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67aa75d7ce60e6c562338102b53ad80c252c11ab601a1eed67e6250d89bcfd84" } } ], "extra": [ 1, 213, 103, 195, 37, 178, 186, 70, 125, 13, 213, 66, 135, 199, 144, 119, 46, 216, 47, 161, 188, 217, 181, 81, 130, 114, 229, 189, 176, 62, 20, 250, 55, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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