Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 516d1c6ffb57008ddb4c74df8c5eef5943fa26d4d66940283dd23c57a7847ed0

Tx prefix hash: bd02ca738215a30b530d82fe095c3775ee4be9dcd2a88f8434c5e0efcf1ce84b
Tx public key: a6bb818be09c96b7c13d91d4917575c903b9f324252ac83b0b6a701357616f40
Timestamp: 1713072961 Timestamp [UCT]: 2024-04-14 05:36:01 Age [y:d:h:m:s]: 01:005:03:12:08
Block: 1000112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264633 RingCT/type: yes/0
Extra: 01a6bb818be09c96b7c13d91d4917575c903b9f324252ac83b0b6a701357616f4002110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f87ccbd6e04c9427e9df979a63878034d6476a57fb8c3992795c1139be26356e 0.600000000000 1460602 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": 1000122, "vin": [ { "gen": { "height": 1000112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f87ccbd6e04c9427e9df979a63878034d6476a57fb8c3992795c1139be26356e" } } ], "extra": [ 1, 166, 187, 129, 139, 224, 156, 150, 183, 193, 61, 145, 212, 145, 117, 117, 201, 3, 185, 243, 36, 37, 42, 200, 59, 11, 106, 112, 19, 87, 97, 111, 64, 2, 17, 0, 0, 0, 14, 89, 218, 211, 245, 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