Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6095b3b4358e81fb224b7442bd64ff63f1ea90549253be3cdb86f2509ef6b05

Tx prefix hash: 679d55e10f8ed36cd6856e2577162ac3044a47da461c42e9e7a59275b7465f3a
Tx public key: 1098d9e188010bd9b0caa8ee73b9ee9d1d94993352ce3daa78bc0041cdaa6333
Timestamp: 1639006624 Timestamp [UCT]: 2021-12-08 23:37:04 Age [y:d:h:m:s]: 03:061:23:17:11
Block: 391386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 823001 RingCT/type: yes/0
Extra: 011098d9e188010bd9b0caa8ee73b9ee9d1d94993352ce3daa78bc0041cdaa6333021100000014536c63bb000000000000000000

1 output(s) for total of 30.986753261000 dcy

stealth address amount amount idx
00: da5635e5f8cd6e075419c68e284c2deaf779302f637357fd99c7422dc8b15798 30.986753261000 787767 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": 391396, "vin": [ { "gen": { "height": 391386 } } ], "vout": [ { "amount": 30986753261, "target": { "key": "da5635e5f8cd6e075419c68e284c2deaf779302f637357fd99c7422dc8b15798" } } ], "extra": [ 1, 16, 152, 217, 225, 136, 1, 11, 217, 176, 202, 168, 238, 115, 185, 238, 157, 29, 148, 153, 51, 82, 206, 61, 170, 120, 188, 0, 65, 205, 170, 99, 51, 2, 17, 0, 0, 0, 20, 83, 108, 99, 187, 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