Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3400f0c09c5975e544a2271f765c28da3e3abf56e4acf7daeca15b4144858c2a

Tx prefix hash: bb7144903f88f9b87ecd47a25da42e22424dc6b0d2eab45b54141aeb0b58ad02
Tx public key: b98950d4c9873018f2337e3e4085224f5a2455864148be56a317bb9885c067b2
Timestamp: 1744921193 Timestamp [UCT]: 2025-04-17 20:19:53 Age [y:d:h:m:s]: 00:218:03:10:20
Block: 1263648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153631 RingCT/type: yes/0
Extra: 01b98950d4c9873018f2337e3e4085224f5a2455864148be56a317bb9885c067b20211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 959a282ab7edda6c8eaa3e89a312b237d28300d73254aa9bf56a9a3d6bdc1351 0.600000000000 1750839 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": 1263658, "vin": [ { "gen": { "height": 1263648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "959a282ab7edda6c8eaa3e89a312b237d28300d73254aa9bf56a9a3d6bdc1351" } } ], "extra": [ 1, 185, 137, 80, 212, 201, 135, 48, 24, 242, 51, 126, 62, 64, 133, 34, 79, 90, 36, 85, 134, 65, 72, 190, 86, 163, 23, 187, 152, 133, 192, 103, 178, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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