Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f46e436934205cff2d6b5cec9b16f935c93cb8d033843b3431b4b1ef05779c0

Tx prefix hash: 409cbfdb0899c74a27cf0bfaf109221378a55160ed19a9c073d1dc763090030b
Tx public key: a8283de68effeeba82d81b1870c098e4ce1a393eb17677726bdaf28520bf79e8
Timestamp: 1577519578 Timestamp [UCT]: 2019-12-28 07:52:58 Age [y:d:h:m:s]: 05:001:11:27:54
Block: 33264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151231 RingCT/type: yes/0
Extra: 01a8283de68effeeba82d81b1870c098e4ce1a393eb17677726bdaf28520bf79e8021100000003d81c26c0000000000000000000

1 output(s) for total of 476.201679488000 dcy

stealth address amount amount idx
00: d37bdef0e7ba2f36b8eaa582f50ba31aa49f33aee5b9eac2edfaf5e565b8a865 476.201679488000 55659 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": 33274, "vin": [ { "gen": { "height": 33264 } } ], "vout": [ { "amount": 476201679488, "target": { "key": "d37bdef0e7ba2f36b8eaa582f50ba31aa49f33aee5b9eac2edfaf5e565b8a865" } } ], "extra": [ 1, 168, 40, 61, 230, 142, 255, 238, 186, 130, 216, 27, 24, 112, 192, 152, 228, 206, 26, 57, 62, 177, 118, 119, 114, 107, 218, 242, 133, 32, 191, 121, 232, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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