Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84b06440de494f06a2cfcee9e6e72e8009bf50d23836ddbcfe32ef77beda19da

Tx prefix hash: 29aad356e07f2614e56b6d6c1a6d89fdb903a17583e908c8e2d71ddb4279c11f
Tx public key: eb1c46e3f93cfc25f751fc73e39d83b49586f5c2576ed42664cc099b2d72fff7
Timestamp: 1701680800 Timestamp [UCT]: 2023-12-04 09:06:40 Age [y:d:h:m:s]: 01:038:04:03:53
Block: 905671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288659 RingCT/type: yes/0
Extra: 01eb1c46e3f93cfc25f751fc73e39d83b49586f5c2576ed42664cc099b2d72fff702110000000233af99f4000000000000000000

1 output(s) for total of 0.612542166000 dcy

stealth address amount amount idx
00: 23f3fc3e7bb7c85dc48136416178c1f3d880162a38f4616356d7ccc0d1163f81 0.612542166000 1362568 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": 905681, "vin": [ { "gen": { "height": 905671 } } ], "vout": [ { "amount": 612542166, "target": { "key": "23f3fc3e7bb7c85dc48136416178c1f3d880162a38f4616356d7ccc0d1163f81" } } ], "extra": [ 1, 235, 28, 70, 227, 249, 60, 252, 37, 247, 81, 252, 115, 227, 157, 131, 180, 149, 134, 245, 194, 87, 110, 212, 38, 100, 204, 9, 155, 45, 114, 255, 247, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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