Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e4343da74904bc6c1a89560647b29b290e0fcc08de123f05f74770a2003a65b

Tx prefix hash: cc86bd6ceed60158a19fb3c173fac3443e3e4e0ac7a802f9985695e2391da36e
Tx public key: d7bccc6d76403c017b1ef82e0f2b6527cc8ac9cd6b143ec1b5f74462acd84037
Timestamp: 1649240345 Timestamp [UCT]: 2022-04-06 10:19:05 Age [y:d:h:m:s]: 02:262:07:11:51
Block: 474349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 707268 RingCT/type: yes/0
Extra: 01d7bccc6d76403c017b1ef82e0f2b6527cc8ac9cd6b143ec1b5f74462acd84037021100000011c9067537000000000000000000

1 output(s) for total of 16.454515324000 dcy

stealth address amount amount idx
00: 7881f8f9c85a8ceacc79d1ae593cf79e8f0023f1e6fc86eb7cf013ada071514d 16.454515324000 894372 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": 474359, "vin": [ { "gen": { "height": 474349 } } ], "vout": [ { "amount": 16454515324, "target": { "key": "7881f8f9c85a8ceacc79d1ae593cf79e8f0023f1e6fc86eb7cf013ada071514d" } } ], "extra": [ 1, 215, 188, 204, 109, 118, 64, 60, 1, 123, 30, 248, 46, 15, 43, 101, 39, 204, 138, 201, 205, 107, 20, 62, 193, 181, 247, 68, 98, 172, 216, 64, 55, 2, 17, 0, 0, 0, 17, 201, 6, 117, 55, 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