Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 058f2b22e2877ac9bbebb725d65db14b5db43da804b3724483c8cb7c478aad98

Tx prefix hash: 1f33cd6635d517d5080f64ec0a5d27255254b2f0e0ab8f5e865a3f8d7623b69e
Tx public key: 33a2ae4db354d6a7b2270cef0836b43b279af54dffc7c538386b2c29e7dda61f
Timestamp: 1743105115 Timestamp [UCT]: 2025-03-27 19:51:55 Age [y:d:h:m:s]: 00:237:06:25:12
Block: 1248604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167335 RingCT/type: yes/0
Extra: 0133a2ae4db354d6a7b2270cef0836b43b279af54dffc7c538386b2c29e7dda61f021100000008165b77a1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 755ae173501527d73e8f6822eb15d53ebbaaa758e12dcf59bab2c77d2e7c9450 0.600000000000 1735637 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": 1248614, "vin": [ { "gen": { "height": 1248604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "755ae173501527d73e8f6822eb15d53ebbaaa758e12dcf59bab2c77d2e7c9450" } } ], "extra": [ 1, 51, 162, 174, 77, 179, 84, 214, 167, 178, 39, 12, 239, 8, 54, 180, 59, 39, 154, 245, 77, 255, 199, 197, 56, 56, 107, 44, 41, 231, 221, 166, 31, 2, 17, 0, 0, 0, 8, 22, 91, 119, 161, 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