Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dced021ac3792546778c6511ea9dd2e815c0f9a34aca10ddff41ac6cbc763b64

Tx prefix hash: 92408b1aaa8f3338d0890e73b2a0bbb83d927b7775bfc6d3c1c65b7ec91cf29e
Tx public key: 465fd12646b651f67264e9071cff0142a79b7ca499adb2b82eabe3b18c288266
Timestamp: 1583754256 Timestamp [UCT]: 2020-03-09 11:44:16 Age [y:d:h:m:s]: 04:210:04:22:33
Block: 79497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1044878 RingCT/type: yes/0
Extra: 01465fd12646b651f67264e9071cff0142a79b7ca499adb2b82eabe3b18c288266021100000041995a6b02000000000000000000

1 output(s) for total of 334.652619583000 dcy

stealth address amount amount idx
00: 23a565668d13caa7b143b6b5a4b8c3db349d248d53db50ff14f23b024518e64e 334.652619583000 145363 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": 79507, "vin": [ { "gen": { "height": 79497 } } ], "vout": [ { "amount": 334652619583, "target": { "key": "23a565668d13caa7b143b6b5a4b8c3db349d248d53db50ff14f23b024518e64e" } } ], "extra": [ 1, 70, 95, 209, 38, 70, 182, 81, 246, 114, 100, 233, 7, 28, 255, 1, 66, 167, 155, 124, 164, 153, 173, 178, 184, 46, 171, 227, 177, 140, 40, 130, 102, 2, 17, 0, 0, 0, 65, 153, 90, 107, 2, 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