Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aa0b1529a8ccdb073143163b5e7f817a90d6dd3e50540eacd6701b321eea9b7

Tx prefix hash: 442b0f07d2d1706671d4171cc550cf7928fb266a2f51f40c593217e1c4c7cb91
Tx public key: ba79e52358e68a667328e45c9521781cde77730a90c8a370522ef8761234ffd0
Timestamp: 1692143837 Timestamp [UCT]: 2023-08-15 23:57:17 Age [y:d:h:m:s]: 01:245:12:47:46
Block: 826779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436644 RingCT/type: yes/0
Extra: 01ba79e52358e68a667328e45c9521781cde77730a90c8a370522ef8761234ffd002110000000533af99f4000000000000000000

1 output(s) for total of 1.118247797000 dcy

stealth address amount amount idx
00: 0970ed365adf5a8d3e020bad6d32721ca903f60ba6d473ae7f0edb4e048d8188 1.118247797000 1279071 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": 826789, "vin": [ { "gen": { "height": 826779 } } ], "vout": [ { "amount": 1118247797, "target": { "key": "0970ed365adf5a8d3e020bad6d32721ca903f60ba6d473ae7f0edb4e048d8188" } } ], "extra": [ 1, 186, 121, 229, 35, 88, 230, 138, 102, 115, 40, 228, 92, 149, 33, 120, 28, 222, 119, 115, 10, 144, 200, 163, 112, 82, 46, 248, 118, 18, 52, 255, 208, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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