Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3badd019f85874845dd82239beb72492e816933c113f1121ea5992f30c196cbb

Tx prefix hash: 4331d55cfe4285aa6885e0329d99d120435d9195559a2914b50b4f8143f6ed66
Tx public key: 764f359f2c45789c94f4bd82df51632e6b21dc990f6ececb43c1d653df76d844
Timestamp: 1698637969 Timestamp [UCT]: 2023-10-30 03:52:49 Age [y:d:h:m:s]: 01:156:10:33:37
Block: 880665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372797 RingCT/type: yes/0
Extra: 01764f359f2c45789c94f4bd82df51632e6b21dc990f6ececb43c1d653df76d844021100000008faf35c9c000000000000000000

1 output(s) for total of 0.741295366000 dcy

stealth address amount amount idx
00: c6a8568dd1d8cfab8475a3b734f87ee37d217c3de87d1eb42d8ba23e9baff549 0.741295366000 1336229 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": 880675, "vin": [ { "gen": { "height": 880665 } } ], "vout": [ { "amount": 741295366, "target": { "key": "c6a8568dd1d8cfab8475a3b734f87ee37d217c3de87d1eb42d8ba23e9baff549" } } ], "extra": [ 1, 118, 79, 53, 159, 44, 69, 120, 156, 148, 244, 189, 130, 223, 81, 99, 46, 107, 33, 220, 153, 15, 110, 206, 203, 67, 193, 214, 83, 223, 118, 216, 68, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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