Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8799803a125b9d94c988652a60f11b83e7194ba0fa6edddcda6120115a42dda1

Tx prefix hash: 965a45789c0a8f717baf0ce2dac15ae852321fa6de4fbb0ccee48649abf8fc8a
Tx public key: 547b804d41bcece4da952026fec9a9baf0d7cbd840d2fa26e5843eb768ceadb2
Timestamp: 1583891852 Timestamp [UCT]: 2020-03-11 01:57:32 Age [y:d:h:m:s]: 04:251:11:24:32
Block: 80179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074815 RingCT/type: yes/0
Extra: 01547b804d41bcece4da952026fec9a9baf0d7cbd840d2fa26e5843eb768ceadb20211000000023b1b9791000000000000000000

1 output(s) for total of 332.915855021000 dcy

stealth address amount amount idx
00: f76d9b56e83d6fe1f8ebf51cce90fdd2b7bbbab3cd7c27de5032a4bec774a5db 332.915855021000 146727 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": 80189, "vin": [ { "gen": { "height": 80179 } } ], "vout": [ { "amount": 332915855021, "target": { "key": "f76d9b56e83d6fe1f8ebf51cce90fdd2b7bbbab3cd7c27de5032a4bec774a5db" } } ], "extra": [ 1, 84, 123, 128, 77, 65, 188, 236, 228, 218, 149, 32, 38, 254, 201, 169, 186, 240, 215, 203, 216, 64, 210, 250, 38, 229, 132, 62, 183, 104, 206, 173, 178, 2, 17, 0, 0, 0, 2, 59, 27, 151, 145, 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