Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04a6276fda6583463998ac694b63ca75343d68e57fda80d4cd808d0212e42481

Tx prefix hash: 355b113b47cbba3faf8b93681ed34f3b909368aee01d3abaacd1e8f4aa3ea112
Tx public key: 3b7bba48929f80c9065883e732a2a52e70860e5ce345824176de27b9c06a586d
Timestamp: 1639367332 Timestamp [UCT]: 2021-12-13 03:48:52 Age [y:d:h:m:s]: 02:330:15:16:13
Block: 394358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 754362 RingCT/type: yes/0
Extra: 013b7bba48929f80c9065883e732a2a52e70860e5ce345824176de27b9c06a586d0211000000020eb261b4000000000000000000

1 output(s) for total of 30.292045459000 dcy

stealth address amount amount idx
00: cf6858721b1f2fb41e8955f37d89b4e5b7773ad3c128633779a99acf96d8d807 30.292045459000 791915 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": 394368, "vin": [ { "gen": { "height": 394358 } } ], "vout": [ { "amount": 30292045459, "target": { "key": "cf6858721b1f2fb41e8955f37d89b4e5b7773ad3c128633779a99acf96d8d807" } } ], "extra": [ 1, 59, 123, 186, 72, 146, 159, 128, 201, 6, 88, 131, 231, 50, 162, 165, 46, 112, 134, 14, 92, 227, 69, 130, 65, 118, 222, 39, 185, 192, 106, 88, 109, 2, 17, 0, 0, 0, 2, 14, 178, 97, 180, 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