Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 329d60eeec0428abba6bd031c17de3439443c79ee5aade882d62c35ce3956bee

Tx prefix hash: e46a4db5be2cd66ec5afafdc7864f929be59c8b33e86384b4a3ee17cb079d893
Tx public key: 6d66094b5010e877f2f4e8dfbd9bb93665aa956d3be9629c7f0fb4c00e1d9f85
Timestamp: 1699424266 Timestamp [UCT]: 2023-11-08 06:17:46 Age [y:d:h:m:s]: 02:001:12:13:47
Block: 886977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520854 RingCT/type: yes/0
Extra: 016d66094b5010e877f2f4e8dfbd9bb93665aa956d3be9629c7f0fb4c00e1d9f8502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.706442794000 dcy

stealth address amount amount idx
00: 4313d3be546f4baaa831e1e54d9edeecb84be41b0dfa794a7ce4685ea1160446 0.706442794000 1342826 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": 886987, "vin": [ { "gen": { "height": 886977 } } ], "vout": [ { "amount": 706442794, "target": { "key": "4313d3be546f4baaa831e1e54d9edeecb84be41b0dfa794a7ce4685ea1160446" } } ], "extra": [ 1, 109, 102, 9, 75, 80, 16, 232, 119, 242, 244, 232, 223, 189, 155, 185, 54, 101, 170, 149, 109, 59, 233, 98, 156, 127, 15, 180, 192, 14, 29, 159, 133, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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