Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61da604d4cb07945e5e471d7c3e0fc618d5b220ec4cd1a36ddcdb9017a11224e

Tx prefix hash: 8e5cf12d4edea0a68051f2ac96281d2310b7c0dde1588501f3df6aa1f5fdd141
Tx public key: 3c603a73c29540836608a69689732e1a228ee14dcd67182b6d4e3975861a29fa
Timestamp: 1751975055 Timestamp [UCT]: 2025-07-08 11:44:15 Age [y:d:h:m:s]: 00:180:14:09:09
Block: 1321285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127582 RingCT/type: yes/0
Extra: 013c603a73c29540836608a69689732e1a228ee14dcd67182b6d4e3975861a29fa0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f44a9a5ee8b4161f3ad7b70c32250e63f09a5fdff925680eda87c7c403b87fcb 0.600000000000 1808990 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": 1321295, "vin": [ { "gen": { "height": 1321285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f44a9a5ee8b4161f3ad7b70c32250e63f09a5fdff925680eda87c7c403b87fcb" } } ], "extra": [ 1, 60, 96, 58, 115, 194, 149, 64, 131, 102, 8, 166, 150, 137, 115, 46, 26, 34, 142, 225, 77, 205, 103, 24, 43, 109, 78, 57, 117, 134, 26, 41, 250, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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