Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1078643b87419936ff796c0b16d3de9d81c57c477f011862c3e0b91f760437ba

Tx prefix hash: 1a7e54e350815f582bfd98102cd8d0bf49fdccec8cc26dead1275c7d64fd18d5
Tx public key: b7a03901dd2390c5e59f9a65893fa1a12d36aff68aac331a665e60ff6a8721fe
Timestamp: 1579078157 Timestamp [UCT]: 2020-01-15 08:49:17 Age [y:d:h:m:s]: 04:316:15:32:35
Block: 45929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115824 RingCT/type: yes/0
Extra: 01b7a03901dd2390c5e59f9a65893fa1a12d36aff68aac331a665e60ff6a8721fe021100000100b221b3d1000000000000000000

1 output(s) for total of 432.341076641000 dcy

stealth address amount amount idx
00: 83b15d724df7d98d75142d4c71dfec650c45965ce8d40d85fefabd0e76b7d092 432.341076641000 84205 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": 45939, "vin": [ { "gen": { "height": 45929 } } ], "vout": [ { "amount": 432341076641, "target": { "key": "83b15d724df7d98d75142d4c71dfec650c45965ce8d40d85fefabd0e76b7d092" } } ], "extra": [ 1, 183, 160, 57, 1, 221, 35, 144, 197, 229, 159, 154, 101, 137, 63, 161, 161, 45, 54, 175, 246, 138, 172, 51, 26, 102, 94, 96, 255, 106, 135, 33, 254, 2, 17, 0, 0, 1, 0, 178, 33, 179, 209, 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