Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484f6b1c4ba7b0739fda9804dfd508618b28c0f0ab3b6a26b5560f248629c232

Tx prefix hash: ee79ae3d715bcfa3ffa9faa6d579a8ef39f9d19649b010ec0db9cb67dda152ac
Tx public key: 046b2a041ee7d4a74d480d6a0f36107d960b4698696b69e14a69c383579455ba
Timestamp: 1736736823 Timestamp [UCT]: 2025-01-13 02:53:43 Age [y:d:h:m:s]: 00:309:00:57:42
Block: 1196168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218380 RingCT/type: yes/0
Extra: 01046b2a041ee7d4a74d480d6a0f36107d960b4698696b69e14a69c383579455ba0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ef3e53b31c1fd1510b7f7989dd556f1418ddbb4200faea8547d78c1d2fa4020 0.600000000000 1682765 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": 1196178, "vin": [ { "gen": { "height": 1196168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ef3e53b31c1fd1510b7f7989dd556f1418ddbb4200faea8547d78c1d2fa4020" } } ], "extra": [ 1, 4, 107, 42, 4, 30, 231, 212, 167, 77, 72, 13, 106, 15, 54, 16, 125, 150, 11, 70, 152, 105, 107, 105, 225, 74, 105, 195, 131, 87, 148, 85, 186, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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