Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624735c477f5f154f40732afc6bbb98ed2761a79ff6db26426e6509b17b97b02

Tx prefix hash: 66786413a5c19096765ffd3680b093d7161f8a420215ae70cd0e37fa59ae2e70
Tx public key: b6f879980e603e44f2c84434ad8d171393b2b3b8bfb5e1b47a76d2fdda116149
Timestamp: 1682763839 Timestamp [UCT]: 2023-04-29 10:23:59 Age [y:d:h:m:s]: 01:325:16:05:34
Block: 749100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494019 RingCT/type: yes/0
Extra: 01b6f879980e603e44f2c84434ad8d171393b2b3b8bfb5e1b47a76d2fdda116149021100000004b3164c24000000000000000000

1 output(s) for total of 2.022650929000 dcy

stealth address amount amount idx
00: db8ba4e69608aaed8fb245f9ca7ea86c3e9369ff74396d43a3e47967ab198bdd 2.022650929000 1197031 of 0

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": 749110, "vin": [ { "gen": { "height": 749100 } } ], "vout": [ { "amount": 2022650929, "target": { "key": "db8ba4e69608aaed8fb245f9ca7ea86c3e9369ff74396d43a3e47967ab198bdd" } } ], "extra": [ 1, 182, 248, 121, 152, 14, 96, 62, 68, 242, 200, 68, 52, 173, 141, 23, 19, 147, 178, 179, 184, 191, 181, 225, 180, 122, 118, 210, 253, 218, 17, 97, 73, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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