Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68c39f4f0dfd978cf564a7ac8e62ce71f3800ac07c4bfcf8bd7110fda362dcdc

Tx prefix hash: 48cc62e98fe2ea457e6a06f9f9dcffa5879564dfbfb7835526629c596a610346
Tx public key: e71008941d23f7c79b7b7643b354fe6d9757614696d20db201e0024d122b8573
Timestamp: 1718858055 Timestamp [UCT]: 2024-06-20 04:34:15 Age [y:d:h:m:s]: 01:143:12:44:16
Block: 1048089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361132 RingCT/type: yes/0
Extra: 01e71008941d23f7c79b7b7643b354fe6d9757614696d20db201e0024d122b857302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de4b620e82de0472a4fb9fd275ed615f122da1b2d5bc269c6236d9b2d400cbe9 0.600000000000 1518084 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": 1048099, "vin": [ { "gen": { "height": 1048089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de4b620e82de0472a4fb9fd275ed615f122da1b2d5bc269c6236d9b2d400cbe9" } } ], "extra": [ 1, 231, 16, 8, 148, 29, 35, 247, 199, 155, 123, 118, 67, 179, 84, 254, 109, 151, 87, 97, 70, 150, 210, 13, 178, 1, 224, 2, 77, 18, 43, 133, 115, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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