Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0eac51976f963ecd42d2add5b1719b2344d413dd6aa2e8e207738b418624cfd

Tx prefix hash: 3ebf9c30d14bb58175141d998608829604880b1087cba4b4ddab5813702b93f3
Tx public key: 9ebe5f2e0646bcf7ec9c1550e1d41d4d2e096b942a759a4fef59dcfc3c365385
Timestamp: 1737719433 Timestamp [UCT]: 2025-01-24 11:50:33 Age [y:d:h:m:s]: 00:149:08:07:28
Block: 1204266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106379 RingCT/type: yes/0
Extra: 019ebe5f2e0646bcf7ec9c1550e1d41d4d2e096b942a759a4fef59dcfc3c3653850211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e769aa25b808e624080d825f591812517ca77ee69063529dea4ccf63ff82c4fc 0.600000000000 1690951 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": 1204276, "vin": [ { "gen": { "height": 1204266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e769aa25b808e624080d825f591812517ca77ee69063529dea4ccf63ff82c4fc" } } ], "extra": [ 1, 158, 190, 95, 46, 6, 70, 188, 247, 236, 156, 21, 80, 225, 212, 29, 77, 46, 9, 107, 148, 42, 117, 154, 79, 239, 89, 220, 252, 60, 54, 83, 133, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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