Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 234bb75b428af4c2d791de7dc91c8c9e4477e626313179fd9104a7c14223742a

Tx prefix hash: 6636f87910450321562bb4a4662e110b87e7a099ac8d338dd274e27fcea39d97
Tx public key: fcc7aee94b7cbe9f68b56d46a1771f089e88e1db87d962f5eef057019c055793
Timestamp: 1712541179 Timestamp [UCT]: 2024-04-08 01:52:59 Age [y:d:h:m:s]: 01:002:20:50:14
Block: 995683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263035 RingCT/type: yes/0
Extra: 01fcc7aee94b7cbe9f68b56d46a1771f089e88e1db87d962f5eef057019c05579302110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fde83fc43c47c20e64deb3360f6119f2ab4489c97f5a2ae63408b15ef5f1d5bb 0.600000000000 1456097 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": 995693, "vin": [ { "gen": { "height": 995683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fde83fc43c47c20e64deb3360f6119f2ab4489c97f5a2ae63408b15ef5f1d5bb" } } ], "extra": [ 1, 252, 199, 174, 233, 75, 124, 190, 159, 104, 181, 109, 70, 161, 119, 31, 8, 158, 136, 225, 219, 135, 217, 98, 245, 238, 240, 87, 1, 156, 5, 87, 147, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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