Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d03f65854284a51743018b4669c6fa987315a38459acaa77a04b933e5fc2669f

Tx prefix hash: 47a8ba80664cd7e4f92c567476542e29ef7e33c9edd918a34b3fd0c8afddee39
Tx public key: f83369674e2fc2cc9e9bbf002398d36236d0d808323d04106b18382d9e89291b
Timestamp: 1711856196 Timestamp [UCT]: 2024-03-31 03:36:36 Age [y:d:h:m:s]: 01:010:00:53:19
Block: 990061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268115 RingCT/type: yes/0
Extra: 01f83369674e2fc2cc9e9bbf002398d36236d0d808323d04106b18382d9e89291b0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcc53ad0054e0403aad733ea2c9ed7d3d2c83dca8a1f87902a7d91aee3c975f0 0.600000000000 1450381 of 15

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": 990071, "vin": [ { "gen": { "height": 990061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcc53ad0054e0403aad733ea2c9ed7d3d2c83dca8a1f87902a7d91aee3c975f0" } } ], "extra": [ 1, 248, 51, 105, 103, 78, 47, 194, 204, 158, 155, 191, 0, 35, 152, 211, 98, 54, 208, 216, 8, 50, 61, 4, 16, 107, 24, 56, 45, 158, 137, 41, 27, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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