Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf6c217341d643a07a1d2af0fd5f18c2f98affd8c3adb95646194f7f4479154

Tx prefix hash: 4f05832696cff6100d4fa018e8d7dd75c94d98e6f3e2761377cb03102b5dacaa
Tx public key: 1aad88eaa535634bbd40b823799ed5860a3202d84a96a40017be06964a218abf
Timestamp: 1707541313 Timestamp [UCT]: 2024-02-10 05:01:53 Age [y:d:h:m:s]: 01:051:08:16:52
Block: 954253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297737 RingCT/type: yes/0
Extra: 011aad88eaa535634bbd40b823799ed5860a3202d84a96a40017be06964a218abf0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7349da6e78d60388b61e4845d553ec320ea4539740b1fd4e276d8b226f553ed6 0.600000000000 1413531 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": 954263, "vin": [ { "gen": { "height": 954253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7349da6e78d60388b61e4845d553ec320ea4539740b1fd4e276d8b226f553ed6" } } ], "extra": [ 1, 26, 173, 136, 234, 165, 53, 99, 75, 189, 64, 184, 35, 121, 158, 213, 134, 10, 50, 2, 216, 74, 150, 164, 0, 23, 190, 6, 150, 74, 33, 138, 191, 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