Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 682a6bea6b9a41a27c06fb8f258cd0780c76c9ba30f1031648ece1bc344326c6

Tx prefix hash: 0edf86c48bf29ae3900ffa34c7d208c81b79084c46718066135dea9e27958103
Tx public key: 5a66f5122639d626c0bcc97bdc38ea5a26f982f0caced060dfd5a35745a12cf1
Timestamp: 1631593601 Timestamp [UCT]: 2021-09-14 04:26:41 Age [y:d:h:m:s]: 03:107:06:13:54
Block: 333394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 852266 RingCT/type: yes/0
Extra: 015a66f5122639d626c0bcc97bdc38ea5a26f982f0caced060dfd5a35745a12cf10211000000063fc41461000000000000000000

1 output(s) for total of 48.231161548000 dcy

stealth address amount amount idx
00: f964919967a9748755b12228e4ae63c8a0fc85a7c4e3f1cefd47d3bc284fee75 48.231161548000 688011 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": 333404, "vin": [ { "gen": { "height": 333394 } } ], "vout": [ { "amount": 48231161548, "target": { "key": "f964919967a9748755b12228e4ae63c8a0fc85a7c4e3f1cefd47d3bc284fee75" } } ], "extra": [ 1, 90, 102, 245, 18, 38, 57, 214, 38, 192, 188, 201, 123, 220, 56, 234, 90, 38, 249, 130, 240, 202, 206, 208, 96, 223, 213, 163, 87, 69, 161, 44, 241, 2, 17, 0, 0, 0, 6, 63, 196, 20, 97, 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