Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364213aa8c7f892e3b59292fff16decd4ec59421076f72c3bc1b3edeba530e1b

Tx prefix hash: 588b1b342317974b86c1a91ae174162d8e3d8bae85a2edd74f32d67644932a5b
Tx public key: 6f9e7e0f27cb482154d3bf59d15a9267361ac2e75daa64691d8d0de9c5eaee12
Timestamp: 1698232100 Timestamp [UCT]: 2023-10-25 11:08:20 Age [y:d:h:m:s]: 01:096:12:00:52
Block: 877305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329945 RingCT/type: yes/0
Extra: 016f9e7e0f27cb482154d3bf59d15a9267361ac2e75daa64691d8d0de9c5eaee120211000000044b8f5122000000000000000000

1 output(s) for total of 0.760544036000 dcy

stealth address amount amount idx
00: 2a97d04ff8d23a5941938b16dd1e4f65eb6fb308cbeb26cebb6486d80010d2ff 0.760544036000 1332675 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": 877315, "vin": [ { "gen": { "height": 877305 } } ], "vout": [ { "amount": 760544036, "target": { "key": "2a97d04ff8d23a5941938b16dd1e4f65eb6fb308cbeb26cebb6486d80010d2ff" } } ], "extra": [ 1, 111, 158, 126, 15, 39, 203, 72, 33, 84, 211, 191, 89, 209, 90, 146, 103, 54, 26, 194, 231, 93, 170, 100, 105, 29, 141, 13, 233, 197, 234, 238, 18, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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