Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3bb12e8beae29d205aa86c21e8eb5237a3a81abc115628172340f2300a2003

Tx prefix hash: d4fe2d5dd567e511ecd323c8d1066f703d80a993c054172c114b4d7ebff1e5f8
Tx public key: 166f9e5897d19cf5083bd28b98f204ea2af9804b26b939e4e2a7e4136612ece2
Timestamp: 1675600537 Timestamp [UCT]: 2023-02-05 12:35:37 Age [y:d:h:m:s]: 02:073:20:09:25
Block: 690345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574400 RingCT/type: yes/0
Extra: 01166f9e5897d19cf5083bd28b98f204ea2af9804b26b939e4e2a7e4136612ece20211000000035029cbac000000000000000000

1 output(s) for total of 3.166652200000 dcy

stealth address amount amount idx
00: d4ed8364c7374b099d13e33a084b625d4165ef9bd5520b63b2b09176324b0de6 3.166652200000 1133067 of 0

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": 690355, "vin": [ { "gen": { "height": 690345 } } ], "vout": [ { "amount": 3166652200, "target": { "key": "d4ed8364c7374b099d13e33a084b625d4165ef9bd5520b63b2b09176324b0de6" } } ], "extra": [ 1, 22, 111, 158, 88, 151, 209, 156, 245, 8, 59, 210, 139, 152, 242, 4, 234, 42, 249, 128, 75, 38, 185, 57, 228, 226, 167, 228, 19, 102, 18, 236, 226, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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