Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04de252102d9f687fa53b728a94ca27dc30c345e2ddfcb42c5d36d4628ec82a1

Tx prefix hash: b92a97d4634c4e4cd9b7d5478b36c1ebf6d0714b592db6d5f28ed7d9286aad50
Tx public key: 8d282437e585d4e767a64cc5068b6bdacbde8a465b139fd68747dc7640f398a8
Timestamp: 1747699515 Timestamp [UCT]: 2025-05-20 00:05:15 Age [y:d:h:m:s]: 00:185:15:51:04
Block: 1286661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130382 RingCT/type: yes/0
Extra: 018d282437e585d4e767a64cc5068b6bdacbde8a465b139fd68747dc7640f398a80211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd41c3844a730e522c1fd77e9e59764e3f2a72489afa9965c4b605905ef4d731 0.600000000000 1774128 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": 1286671, "vin": [ { "gen": { "height": 1286661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd41c3844a730e522c1fd77e9e59764e3f2a72489afa9965c4b605905ef4d731" } } ], "extra": [ 1, 141, 40, 36, 55, 229, 133, 212, 231, 103, 166, 76, 197, 6, 139, 107, 218, 203, 222, 138, 70, 91, 19, 159, 214, 135, 71, 220, 118, 64, 243, 152, 168, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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