Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b001d6c2ae16c890cd11fb73a076f4b506518f9936557ed169b63bea403da95

Tx prefix hash: 3a6b9e1c83a08d076d953d00aa76ae8a2f71d463c41a46e30d0f9091872196df
Tx public key: bb2372a79381d493645db8e0548bd8a5e6b3423100aa15bcd1102fa8adc76d10
Timestamp: 1701106276 Timestamp [UCT]: 2023-11-27 17:31:16 Age [y:d:h:m:s]: 01:198:16:07:34
Block: 900913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403142 RingCT/type: yes/0
Extra: 01bb2372a79381d493645db8e0548bd8a5e6b3423100aa15bcd1102fa8adc76d1002110000000675e3f0e9000000000000000000

1 output(s) for total of 0.635186452000 dcy

stealth address amount amount idx
00: 9e6f7acb220e39a5506d776a6b1a531d0f1cab19ec2c8eac8642f8cc87212e97 0.635186452000 1357440 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": 900923, "vin": [ { "gen": { "height": 900913 } } ], "vout": [ { "amount": 635186452, "target": { "key": "9e6f7acb220e39a5506d776a6b1a531d0f1cab19ec2c8eac8642f8cc87212e97" } } ], "extra": [ 1, 187, 35, 114, 167, 147, 129, 212, 147, 100, 93, 184, 224, 84, 139, 216, 165, 230, 179, 66, 49, 0, 170, 21, 188, 209, 16, 47, 168, 173, 199, 109, 16, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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