Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b3fb207afc08601b28f719d6e5d8496b1762ed902ff29a70558e36ab82e87d8

Tx prefix hash: c579bec928480bb70072e6a3ef940c488c2279947e7b2e70462d91baefa68209
Tx public key: 6739ccf5b21b04b42aa8435d4efe6a5177b4cb6c0f7adfd4293465e933071e95
Timestamp: 1704701749 Timestamp [UCT]: 2024-01-08 08:15:49 Age [y:d:h:m:s]: 01:086:21:08:10
Block: 930712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323198 RingCT/type: yes/0
Extra: 016739ccf5b21b04b42aa8435d4efe6a5177b4cb6c0f7adfd4293465e933071e9502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27bbd2cebc55abd5a93ca1973a70e12e123b2b756b52cbe56de78e323ab8133c 0.600000000000 1388600 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": 930722, "vin": [ { "gen": { "height": 930712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27bbd2cebc55abd5a93ca1973a70e12e123b2b756b52cbe56de78e323ab8133c" } } ], "extra": [ 1, 103, 57, 204, 245, 178, 27, 4, 180, 42, 168, 67, 93, 78, 254, 106, 81, 119, 180, 203, 108, 15, 122, 223, 212, 41, 52, 101, 233, 51, 7, 30, 149, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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