Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bbf9a0bae0dff54dcc060eaeba159c72523d7e7dbb01c658156f09e2ff611de

Tx prefix hash: 131c6dc11e60a0c582d84224861b7c9fbb1e83d5709728c63518e45f33620a36
Tx public key: 8be3c84f4786ebb7d544bf4e6f51a9854a8b7a2cb99f68aae90633d928236eee
Timestamp: 1694837280 Timestamp [UCT]: 2023-09-16 04:08:00 Age [y:d:h:m:s]: 01:213:23:58:21
Block: 849128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414040 RingCT/type: yes/0
Extra: 018be3c84f4786ebb7d544bf4e6f51a9854a8b7a2cb99f68aae90633d928236eee021100000003faf35c9c000000000000000000

1 output(s) for total of 0.942945309000 dcy

stealth address amount amount idx
00: 2d8eea4a984b6bd7959f0c56e4246e6c8da63c55e6f49eeb48efd172ea0427ce 0.942945309000 1302772 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": 849138, "vin": [ { "gen": { "height": 849128 } } ], "vout": [ { "amount": 942945309, "target": { "key": "2d8eea4a984b6bd7959f0c56e4246e6c8da63c55e6f49eeb48efd172ea0427ce" } } ], "extra": [ 1, 139, 227, 200, 79, 71, 134, 235, 183, 213, 68, 191, 78, 111, 81, 169, 133, 74, 139, 122, 44, 185, 159, 104, 170, 233, 6, 51, 217, 40, 35, 110, 238, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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