Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb23d3d39358517ddff48b445f871b14d19a927234b391301e84e8d99323fd31

Tx prefix hash: d3f41b761724052541a5c74ab486326041cdf177d1b2eabacc95fe8a4d67739e
Tx public key: 4cd143b9c8d0a43e05fefde5271218c55dcbda6d2f4a38c06b546229bff09e57
Timestamp: 1738190427 Timestamp [UCT]: 2025-01-29 22:40:27 Age [y:d:h:m:s]: 00:137:14:13:56
Block: 1207945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98306 RingCT/type: yes/0
Extra: 014cd143b9c8d0a43e05fefde5271218c55dcbda6d2f4a38c06b546229bff09e57021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c10a8a40f85e539fea920b22a6de6947ba24d6f88e93bba36e6323827648899 0.600000000000 1694672 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": 1207955, "vin": [ { "gen": { "height": 1207945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c10a8a40f85e539fea920b22a6de6947ba24d6f88e93bba36e6323827648899" } } ], "extra": [ 1, 76, 209, 67, 185, 200, 208, 164, 62, 5, 254, 253, 229, 39, 18, 24, 197, 93, 203, 218, 109, 47, 74, 56, 192, 107, 84, 98, 41, 191, 240, 158, 87, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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