Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4632901744cedd2dddced47427c0307e2e4a47725562d02a28794a7b3fe7d4c6

Tx prefix hash: 166291cbb54c9c88b715b16d1210817088b03f1ce28ec1093c51c4c0a65d209a
Tx public key: 3641e3cd1bce33d7eb0aa76d8936e4fed8381b030d4bef5d74469fcc0c8e2e75
Timestamp: 1709153513 Timestamp [UCT]: 2024-02-28 20:51:53 Age [y:d:h:m:s]: 01:049:17:48:21
Block: 967643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296564 RingCT/type: yes/0
Extra: 013641e3cd1bce33d7eb0aa76d8936e4fed8381b030d4bef5d74469fcc0c8e2e7502110000001759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c49752011c57255fadb9c95bb060f46db19aa3cdb8b9f6d2534827dc906442df 0.600000000000 1427426 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": 967653, "vin": [ { "gen": { "height": 967643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c49752011c57255fadb9c95bb060f46db19aa3cdb8b9f6d2534827dc906442df" } } ], "extra": [ 1, 54, 65, 227, 205, 27, 206, 51, 215, 235, 10, 167, 109, 137, 54, 228, 254, 216, 56, 27, 3, 13, 75, 239, 93, 116, 70, 159, 204, 12, 142, 46, 117, 2, 17, 0, 0, 0, 23, 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