Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d9e20bfce466c1a0c3f003d0b15a2e1f76f09eacd04a812bfffa3255678b5df

Tx prefix hash: 080e80f8900333b6a7a173f011454287e2b6209f4023c41359c29c1d4ccb278a
Tx public key: 8fe740b39e60c229eef4a568b0d130b0f50cf85bddeb01aae48cf5d586a4be82
Timestamp: 1702901685 Timestamp [UCT]: 2023-12-18 12:14:45 Age [y:d:h:m:s]: 01:351:14:38:14
Block: 915794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510183 RingCT/type: yes/0
Extra: 018fe740b39e60c229eef4a568b0d130b0f50cf85bddeb01aae48cf5d586a4be82021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2afb1b04d57ebbcc59719ea39c20498a60f5cef37cc8da391cf011a9b09ca69a 0.600000000000 1373226 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": 915804, "vin": [ { "gen": { "height": 915794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2afb1b04d57ebbcc59719ea39c20498a60f5cef37cc8da391cf011a9b09ca69a" } } ], "extra": [ 1, 143, 231, 64, 179, 158, 96, 194, 41, 238, 244, 165, 104, 176, 209, 48, 176, 245, 12, 248, 91, 221, 235, 1, 170, 228, 140, 245, 213, 134, 164, 190, 130, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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