Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dec39bdc5000aa8b8336c06551cba7bac9003d18a5de41b3335ed6c3bbf5a96e

Tx prefix hash: 49e51cabbea9136da157a05e975bf2060b48f756162a373cd053275d6a1717a7
Tx public key: 4f9ef1a9e8f4203f8ee7fbe1e4416636f7c7418274e1bf7bbe53b2c8e55fe549
Timestamp: 1630405681 Timestamp [UCT]: 2021-08-31 10:28:01 Age [y:d:h:m:s]: 03:161:23:24:10
Block: 324475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 890236 RingCT/type: yes/0
Extra: 014f9ef1a9e8f4203f8ee7fbe1e4416636f7c7418274e1bf7bbe53b2c8e55fe5490211000000167062e8e6000000000000000000

1 output(s) for total of 51.627379731000 dcy

stealth address amount amount idx
00: 2d4b3b0c8e385a2aa8036d6c09846b804c7042a1df81ea80c4f94531a8f10683 51.627379731000 672724 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": 324485, "vin": [ { "gen": { "height": 324475 } } ], "vout": [ { "amount": 51627379731, "target": { "key": "2d4b3b0c8e385a2aa8036d6c09846b804c7042a1df81ea80c4f94531a8f10683" } } ], "extra": [ 1, 79, 158, 241, 169, 232, 244, 32, 63, 142, 231, 251, 225, 228, 65, 102, 54, 247, 199, 65, 130, 116, 225, 191, 123, 190, 83, 178, 200, 229, 95, 229, 73, 2, 17, 0, 0, 0, 22, 112, 98, 232, 230, 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