Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 767fc00b76b0f474440110483fe715e041f5886ebbd86ea4bddbda66ef20dce1

Tx prefix hash: 270cc6011404e2810756386e778abc5ac75a523deb167d1b84652358e32e7202
Tx public key: bfa4dd7198277bf64b6f2ae97d4e38f1a208b37d71f0a57db5d8e4729a60bc60
Timestamp: 1695922172 Timestamp [UCT]: 2023-09-28 17:29:32 Age [y:d:h:m:s]: 01:049:02:06:46
Block: 858137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296312 RingCT/type: yes/0
Extra: 01bfa4dd7198277bf64b6f2ae97d4e38f1a208b37d71f0a57db5d8e4729a60bc60021100000001faf35c9c000000000000000000

1 output(s) for total of 0.880310606000 dcy

stealth address amount amount idx
00: ad7b6361f4eaecc2fcf6e0ced0b822b7d0530f44fc199c4cb3022c9f1402b0ce 0.880310606000 1312301 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": 858147, "vin": [ { "gen": { "height": 858137 } } ], "vout": [ { "amount": 880310606, "target": { "key": "ad7b6361f4eaecc2fcf6e0ced0b822b7d0530f44fc199c4cb3022c9f1402b0ce" } } ], "extra": [ 1, 191, 164, 221, 113, 152, 39, 123, 246, 75, 111, 42, 233, 125, 78, 56, 241, 162, 8, 179, 125, 113, 240, 165, 125, 181, 216, 228, 114, 154, 96, 188, 96, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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