Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc3d87521fccf6dd875290eb85f35e85463bb9988347b597bb627bd8fe841568

Tx prefix hash: 86784ed077ed33677de4b08670eecb30109d585a079d69469c95d3c1b75a7ff8
Tx public key: ca65b2d22b75fa09c7d890f28633ed7d4f3c1e8ae9b1cc8a7b7d3c29ee0f8c9b
Timestamp: 1699438501 Timestamp [UCT]: 2023-11-08 10:15:01 Age [y:d:h:m:s]: 01:050:04:38:04
Block: 887100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297264 RingCT/type: yes/0
Extra: 01ca65b2d22b75fa09c7d890f28633ed7d4f3c1e8ae9b1cc8a7b7d3c29ee0f8c9b02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.705780166000 dcy

stealth address amount amount idx
00: e95416cb3b8185640f9ffbe9eca6c6defcc92b39c6bb126c07a1404b13036635 0.705780166000 1342955 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": 887110, "vin": [ { "gen": { "height": 887100 } } ], "vout": [ { "amount": 705780166, "target": { "key": "e95416cb3b8185640f9ffbe9eca6c6defcc92b39c6bb126c07a1404b13036635" } } ], "extra": [ 1, 202, 101, 178, 210, 43, 117, 250, 9, 199, 216, 144, 242, 134, 51, 237, 125, 79, 60, 30, 138, 233, 177, 204, 138, 123, 125, 60, 41, 238, 15, 140, 155, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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