Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47268c6aaea3986e1d7f1ee80394bebcf9f6db23e1c2318e2d57308750fba928

Tx prefix hash: 128cf0895c17bf8eb646ddfd1f5a1b17da4d5673add47d24d0e689496dcf0a2e
Tx public key: 2b1847cef09240a39975a1c68170c71cdec2bb8d2c7f4433bc4a1043695806bb
Timestamp: 1733360841 Timestamp [UCT]: 2024-12-05 01:07:21 Age [y:d:h:m:s]: 00:116:18:38:34
Block: 1168230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83250 RingCT/type: yes/0
Extra: 012b1847cef09240a39975a1c68170c71cdec2bb8d2c7f4433bc4a1043695806bb0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 253327d77d1e13841f4ff0c31d82ad39c394d5be4df3f0140fd72f1575aa2eec 0.600000000000 1653937 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": 1168240, "vin": [ { "gen": { "height": 1168230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "253327d77d1e13841f4ff0c31d82ad39c394d5be4df3f0140fd72f1575aa2eec" } } ], "extra": [ 1, 43, 24, 71, 206, 240, 146, 64, 163, 153, 117, 161, 198, 129, 112, 199, 28, 222, 194, 187, 141, 44, 127, 68, 51, 188, 74, 16, 67, 105, 88, 6, 187, 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