Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4516a8c858134272bc2c975a9f0fd38cc2ef87504bc01d9fe7e21fd9ad724d5

Tx prefix hash: a0c8c1a3846f95bc67bb740d79ab56008028298ce4b500df5c2d3462f02f2b72
Tx public key: cea09df6ddb4fbaf9a98b4a46fcde94186c4b9da8ec7406b7ce7b871f4d97bb3
Timestamp: 1730879036 Timestamp [UCT]: 2024-11-06 07:43:56 Age [y:d:h:m:s]: 01:008:02:21:52
Block: 1147659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264217 RingCT/type: yes/0
Extra: 01cea09df6ddb4fbaf9a98b4a46fcde94186c4b9da8ec7406b7ce7b871f4d97bb30211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae786103eb79c44cd0794afe9ea1641bc52aaaaf0cbe82df2c1eb13ae22068d 0.600000000000 1632358 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": 1147669, "vin": [ { "gen": { "height": 1147659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae786103eb79c44cd0794afe9ea1641bc52aaaaf0cbe82df2c1eb13ae22068d" } } ], "extra": [ 1, 206, 160, 157, 246, 221, 180, 251, 175, 154, 152, 180, 164, 111, 205, 233, 65, 134, 196, 185, 218, 142, 199, 64, 107, 124, 231, 184, 113, 244, 217, 123, 179, 2, 17, 0, 0, 0, 4, 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