Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a338a5eebee644db9b5ecf244843500fc01c1c8d5f4f68fd51ee8f8dea084d20

Tx prefix hash: 53f97d3f4a591c0f2819ce64e760fc6172b6fea87bccdbaf76ddc0a557a00d7b
Tx public key: 63b7e94ecf7d85e5d1c23ae4c8f80ca14e682fa3cc4bcb711b7c33e4063f165a
Timestamp: 1648341455 Timestamp [UCT]: 2022-03-27 00:37:35 Age [y:d:h:m:s]: 03:035:21:44:16
Block: 467132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 805877 RingCT/type: yes/0
Extra: 0163b7e94ecf7d85e5d1c23ae4c8f80ca14e682fa3cc4bcb711b7c33e4063f165a021100000007c9067537000000000000000000

1 output(s) for total of 17.385933812000 dcy

stealth address amount amount idx
00: ee556e15ffb10ae7b4bcafd84b787bf2b0c3a415fcb238a5fe4db1ba98359743 17.385933812000 885579 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": 467142, "vin": [ { "gen": { "height": 467132 } } ], "vout": [ { "amount": 17385933812, "target": { "key": "ee556e15ffb10ae7b4bcafd84b787bf2b0c3a415fcb238a5fe4db1ba98359743" } } ], "extra": [ 1, 99, 183, 233, 78, 207, 125, 133, 229, 209, 194, 58, 228, 200, 248, 12, 161, 78, 104, 47, 163, 204, 75, 203, 113, 27, 124, 51, 228, 6, 63, 22, 90, 2, 17, 0, 0, 0, 7, 201, 6, 117, 55, 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