Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bb83b44a648448eac0fde03ebdd8ca042cb2d3d713548296696d9d40c1e9462

Tx prefix hash: 1777b6139c93a4cd6e53f596d4636c610bcbed2fdaa7a9b3248c330785c8c262
Tx public key: e9e8af35e4ce8f4eb73da10ba797a419dec6652b4ff3a732a4c3da3d4c564324
Timestamp: 1582762361 Timestamp [UCT]: 2020-02-27 00:12:41 Age [y:d:h:m:s]: 04:304:12:40:59
Block: 72461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111164 RingCT/type: yes/0
Extra: 01e9e8af35e4ce8f4eb73da10ba797a419dec6652b4ff3a732a4c3da3d4c5643240211000000374943cd9f000000000000000000

1 output(s) for total of 353.107894342000 dcy

stealth address amount amount idx
00: 8d142cfdf3248d8885626aceff2cd785294f82523e0c1ea4a0e0eb4038ae75d3 353.107894342000 133895 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": 72471, "vin": [ { "gen": { "height": 72461 } } ], "vout": [ { "amount": 353107894342, "target": { "key": "8d142cfdf3248d8885626aceff2cd785294f82523e0c1ea4a0e0eb4038ae75d3" } } ], "extra": [ 1, 233, 232, 175, 53, 228, 206, 143, 78, 183, 61, 161, 11, 167, 151, 164, 25, 222, 198, 101, 43, 79, 243, 167, 50, 164, 195, 218, 61, 76, 86, 67, 36, 2, 17, 0, 0, 0, 55, 73, 67, 205, 159, 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