Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8929d34a90fd6129a961a7e5b0768720caea7a3759129cab6c393f9b12beb1d

Tx prefix hash: f8e7b49a9f0f7f64dbfda700aedaef348a3e275d69428a58c34a7317abdbe293
Tx public key: 664639adbbce1b53020e28b62749e961b1498f80c0ff0510d3991bee774e860b
Timestamp: 1669721432 Timestamp [UCT]: 2022-11-29 11:30:32 Age [y:d:h:m:s]: 02:106:13:29:24
Block: 641634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597866 RingCT/type: yes/0
Extra: 01664639adbbce1b53020e28b62749e961b1498f80c0ff0510d3991bee774e860b02110000000283600029000000000000000000

1 output(s) for total of 4.591982263000 dcy

stealth address amount amount idx
00: b998d8d3c13b450cca8467ee4dc24d6232051e31d7db1c4f2adf2aa4d1089f1d 4.591982263000 1081449 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": 641644, "vin": [ { "gen": { "height": 641634 } } ], "vout": [ { "amount": 4591982263, "target": { "key": "b998d8d3c13b450cca8467ee4dc24d6232051e31d7db1c4f2adf2aa4d1089f1d" } } ], "extra": [ 1, 102, 70, 57, 173, 187, 206, 27, 83, 2, 14, 40, 182, 39, 73, 233, 97, 177, 73, 143, 128, 192, 255, 5, 16, 211, 153, 27, 238, 119, 78, 134, 11, 2, 17, 0, 0, 0, 2, 131, 96, 0, 41, 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