Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2164e095aba7ab1fa91f6db037a5b3454e0d0b6c743fd8ebe5119532a5e739a4

Tx prefix hash: be83443da46314461103e089f2ff6bc9edbbd3ae9c0840de29483499cc37329d
Tx public key: a39cee5f2ccdcccf201e29178f1cc28146a67e91f9b49c65eff64301a98a00a1
Timestamp: 1672526271 Timestamp [UCT]: 2022-12-31 22:37:51 Age [y:d:h:m:s]: 02:096:18:07:32
Block: 664836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590836 RingCT/type: yes/0
Extra: 01a39cee5f2ccdcccf201e29178f1cc28146a67e91f9b49c65eff64301a98a00a1021100000003e7ace25d000000000000000000

1 output(s) for total of 3.847001098000 dcy

stealth address amount amount idx
00: 6e0b3c1a16bf154fa0f84642d8e0ce4c38d5b186690d7e18c7b22bf299fe30a4 3.847001098000 1105845 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": 664846, "vin": [ { "gen": { "height": 664836 } } ], "vout": [ { "amount": 3847001098, "target": { "key": "6e0b3c1a16bf154fa0f84642d8e0ce4c38d5b186690d7e18c7b22bf299fe30a4" } } ], "extra": [ 1, 163, 156, 238, 95, 44, 205, 204, 207, 32, 30, 41, 23, 143, 28, 194, 129, 70, 166, 126, 145, 249, 180, 156, 101, 239, 246, 67, 1, 169, 138, 0, 161, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 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