Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 661e38a82f9e2aa3cbefd4438e800bf2b4f7337ee0264d6fa8fdbe77910702ba

Tx prefix hash: 71d84f5ad5e15d2ecdf756aab451af15a1e2d50b52d53dd3e5ca4c9cd8eb5a47
Tx public key: 818c93d7aea9a995d8fac361f51b4b7f10a592819f4ce24d6e603f3f92e09ef6
Timestamp: 1741481651 Timestamp [UCT]: 2025-03-09 00:54:11 Age [y:d:h:m:s]: 00:263:21:39:15
Block: 1235191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186373 RingCT/type: yes/0
Extra: 01818c93d7aea9a995d8fac361f51b4b7f10a592819f4ce24d6e603f3f92e09ef6021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58ba4604f59c332b03fd325b7d73a9e4c085b6bcb9da5253dc3bed329e75b430 0.600000000000 1722128 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": 1235201, "vin": [ { "gen": { "height": 1235191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58ba4604f59c332b03fd325b7d73a9e4c085b6bcb9da5253dc3bed329e75b430" } } ], "extra": [ 1, 129, 140, 147, 215, 174, 169, 169, 149, 216, 250, 195, 97, 245, 27, 75, 127, 16, 165, 146, 129, 159, 76, 226, 77, 110, 96, 63, 63, 146, 224, 158, 246, 2, 17, 0, 0, 0, 7, 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