Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc9ec828f4d74b4185f3d79e7378a6f8e006d9cb036a04ef33eb1dad5f998402

Tx prefix hash: ab1bfdc84bcdd12665b2a9b16eaa07fee45133400e4f0d902b8c2b09527fadb7
Tx public key: 9b80dfce3fe5200b9d48fd6ff60e5fe8f0d281706f826060859dfd8d10c8f872
Timestamp: 1583935283 Timestamp [UCT]: 2020-03-11 14:01:23 Age [y:d:h:m:s]: 04:263:12:46:07
Block: 80745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083229 RingCT/type: yes/0
Extra: 019b80dfce3fe5200b9d48fd6ff60e5fe8f0d281706f826060859dfd8d10c8f872021100000002995a6b02000000000000000000

1 output(s) for total of 331.481339403000 dcy

stealth address amount amount idx
00: 15fef76cf08a7ca244af0feb16280342c12dedafa8f044f743f5d12d801739b8 331.481339403000 147663 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": 80755, "vin": [ { "gen": { "height": 80745 } } ], "vout": [ { "amount": 331481339403, "target": { "key": "15fef76cf08a7ca244af0feb16280342c12dedafa8f044f743f5d12d801739b8" } } ], "extra": [ 1, 155, 128, 223, 206, 63, 229, 32, 11, 157, 72, 253, 111, 246, 14, 95, 232, 240, 210, 129, 112, 111, 130, 96, 96, 133, 157, 253, 141, 16, 200, 248, 114, 2, 17, 0, 0, 0, 2, 153, 90, 107, 2, 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