Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b6a3c952f78cc3e212179d1c9b4d1e1a94e0a9e09f76b1973b071bc1ce96e76

Tx prefix hash: e598eec0db6323490124a3a80a98f2d9c20656b9fa96395ab067528967ef1f78
Tx public key: df8217d3d271b30ed4d6fda77e0085df200cd289952dbcf76776d2c2864a60c4
Timestamp: 1703595710 Timestamp [UCT]: 2023-12-26 13:01:50 Age [y:d:h:m:s]: 01:321:10:02:19
Block: 921557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488551 RingCT/type: yes/0
Extra: 01df8217d3d271b30ed4d6fda77e0085df200cd289952dbcf76776d2c2864a60c4021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37859f13962b9290e73b037383c67e06a92c9ce22764858445d9fa9f6251dc7d 0.600000000000 1379245 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": 921567, "vin": [ { "gen": { "height": 921557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37859f13962b9290e73b037383c67e06a92c9ce22764858445d9fa9f6251dc7d" } } ], "extra": [ 1, 223, 130, 23, 211, 210, 113, 179, 14, 212, 214, 253, 167, 126, 0, 133, 223, 32, 12, 210, 137, 149, 45, 188, 247, 103, 118, 210, 194, 134, 74, 96, 196, 2, 17, 0, 0, 0, 2, 173, 86, 148, 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