Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe4c2dfa39b729f8bb0cd80a54da05774843d0636cead599281440f470d925fb

Tx prefix hash: d95c0bc86e4a2b70df7fc0d753b8ed9bfa97e0ca956737eb8cef6b12c2b43c33
Tx public key: 4ac4916028aff21cb9f8de3bc87d68d954d469d825681a930bec4a25cfa4086d
Timestamp: 1721606794 Timestamp [UCT]: 2024-07-22 00:06:34 Age [y:d:h:m:s]: 00:173:17:38:59
Block: 1070858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124320 RingCT/type: yes/0
Extra: 014ac4916028aff21cb9f8de3bc87d68d954d469d825681a930bec4a25cfa4086d021100000002e914dd15000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 1ca9542547566327f8a42ccc9b2bd51106bc61c0fbdc4700d0ca959210459b26 0.615600000000 1542865 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": 1070868, "vin": [ { "gen": { "height": 1070858 } } ], "vout": [ { "amount": 615600000, "target": { "key": "1ca9542547566327f8a42ccc9b2bd51106bc61c0fbdc4700d0ca959210459b26" } } ], "extra": [ 1, 74, 196, 145, 96, 40, 175, 242, 28, 185, 248, 222, 59, 200, 125, 104, 217, 84, 212, 105, 216, 37, 104, 26, 147, 11, 236, 74, 37, 207, 164, 8, 109, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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