Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4d1567e7385ad3f5cfa4cdfc579acb9bd20d32b0f32506c57a87f2c4d635bc

Tx prefix hash: a02ce9ffe750801e428da1704943fc50d41236c980dfc4687d76c73556fafadf
Tx public key: 563a0a68f22ca0cb331a31468d4a1ae5b285fdd13a3c77104801a3243c8be682
Timestamp: 1736092541 Timestamp [UCT]: 2025-01-05 15:55:41 Age [y:d:h:m:s]: 00:165:17:00:33
Block: 1190842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118099 RingCT/type: yes/0
Extra: 01563a0a68f22ca0cb331a31468d4a1ae5b285fdd13a3c77104801a3243c8be6820211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b70f51f1a391a9dd566facdafdf4a2ad81cb9ef269961f50e5eac0ce7048da1 0.600000000000 1677361 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": 1190852, "vin": [ { "gen": { "height": 1190842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b70f51f1a391a9dd566facdafdf4a2ad81cb9ef269961f50e5eac0ce7048da1" } } ], "extra": [ 1, 86, 58, 10, 104, 242, 44, 160, 203, 51, 26, 49, 70, 141, 74, 26, 229, 178, 133, 253, 209, 58, 60, 119, 16, 72, 1, 163, 36, 60, 139, 230, 130, 2, 17, 0, 0, 0, 5, 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