Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5737e63f69cb69b57098b957240fba5423d1b347d6feab3dff2a0048e08545a3

Tx prefix hash: fe55067e03ab6d389433e03d353472a475b5fbf5b0fb091c36d30e09e3d2789f
Tx public key: 179e02386df2f0d49ecea905cb4b79eedab81059babddcebe4590a7a15a80409
Timestamp: 1658379098 Timestamp [UCT]: 2022-07-21 04:51:38 Age [y:d:h:m:s]: 02:264:00:52:19
Block: 548330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 709882 RingCT/type: yes/0
Extra: 01179e02386df2f0d49ecea905cb4b79eedab81059babddcebe4590a7a15a80409021100000003d3fcec30000000000000000000

1 output(s) for total of 9.357400592000 dcy

stealth address amount amount idx
00: 78e393901c63060e376d4a905ab33272929fbb95e0c1a853701c68f6b3cbf61b 9.357400592000 979571 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": 548340, "vin": [ { "gen": { "height": 548330 } } ], "vout": [ { "amount": 9357400592, "target": { "key": "78e393901c63060e376d4a905ab33272929fbb95e0c1a853701c68f6b3cbf61b" } } ], "extra": [ 1, 23, 158, 2, 56, 109, 242, 240, 212, 158, 206, 169, 5, 203, 75, 121, 238, 218, 184, 16, 89, 186, 189, 220, 235, 228, 89, 10, 122, 21, 168, 4, 9, 2, 17, 0, 0, 0, 3, 211, 252, 236, 48, 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