Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdee099b48f1bba605a53f4a53239d761d98730a36ba6e871527f409e9f1a779

Tx prefix hash: b31b1b6ce85f30a3c5bd9b8a9b838ab120f3f04eeccb62d4ac6e40731b213909
Tx public key: b8cc6105e8fd0fd75e16eb853d42a3be3830968c91b1ebbcdbe133d14ef57880
Timestamp: 1672684902 Timestamp [UCT]: 2023-01-02 18:41:42 Age [y:d:h:m:s]: 02:135:12:35:09
Block: 666160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 618573 RingCT/type: yes/0
Extra: 01b8cc6105e8fd0fd75e16eb853d42a3be3830968c91b1ebbcdbe133d14ef5788002110000000352542ceb000000000000000000

1 output(s) for total of 3.808336777000 dcy

stealth address amount amount idx
00: 70231527067d99d64ee4166a57f59948c79c110b6d387a193c540c72171731c4 3.808336777000 1107259 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": 666170, "vin": [ { "gen": { "height": 666160 } } ], "vout": [ { "amount": 3808336777, "target": { "key": "70231527067d99d64ee4166a57f59948c79c110b6d387a193c540c72171731c4" } } ], "extra": [ 1, 184, 204, 97, 5, 232, 253, 15, 215, 94, 22, 235, 133, 61, 66, 163, 190, 56, 48, 150, 140, 145, 177, 235, 188, 219, 225, 51, 209, 78, 245, 120, 128, 2, 17, 0, 0, 0, 3, 82, 84, 44, 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