Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ab7035ac8474f86edf0ad96a50187653c0d8126b21ef0de6d8784478e97d345

Tx prefix hash: 446166bafef26e272021ac00c8e1777e4f0b0bb232e85da31f113f73fca6996a
Tx public key: d841b8a236f18a6932001b03ffc0e1518eaa2176d26531caebe5bc29cc88a61a
Timestamp: 1577872675 Timestamp [UCT]: 2020-01-01 09:57:55 Age [y:d:h:m:s]: 04:310:00:47:31
Block: 36260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110775 RingCT/type: yes/0
Extra: 01d841b8a236f18a6932001b03ffc0e1518eaa2176d26531caebe5bc29cc88a61a02110000008cc5b5978f000000000000000000

1 output(s) for total of 465.432194729000 dcy

stealth address amount amount idx
00: 26a457b5b6a3bcbf8431a0f3f5f799361b75b4a3634c49dbbf192711d9c91bf3 465.432194729000 61375 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": 36270, "vin": [ { "gen": { "height": 36260 } } ], "vout": [ { "amount": 465432194729, "target": { "key": "26a457b5b6a3bcbf8431a0f3f5f799361b75b4a3634c49dbbf192711d9c91bf3" } } ], "extra": [ 1, 216, 65, 184, 162, 54, 241, 138, 105, 50, 0, 27, 3, 255, 192, 225, 81, 142, 170, 33, 118, 210, 101, 49, 202, 235, 229, 188, 41, 204, 136, 166, 26, 2, 17, 0, 0, 0, 140, 197, 181, 151, 143, 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