Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0962af997b9b269df090b5dc558d1cd33ae761ec0593177be9e791bceb77e37

Tx prefix hash: 6772ecb957ce3ae5a5a2a210c79005c727379622be83f28370a4fc50fe0201dd
Tx public key: 13457b3b43c735fce9ea16a06fbefde441648465ef632b8ff1b0acd3b9a45d23
Timestamp: 1582338744 Timestamp [UCT]: 2020-02-22 02:32:24 Age [y:d:h:m:s]: 05:014:13:05:46
Block: 69950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1163536 RingCT/type: yes/0
Extra: 0113457b3b43c735fce9ea16a06fbefde441648465ef632b8ff1b0acd3b9a45d2302110000000303d36d11000000000000000000

1 output(s) for total of 359.937765421000 dcy

stealth address amount amount idx
00: fd8bce12be6c0edae40a626bf293a1df2a91dd6fc02453d214ffcd5984574d1a 359.937765421000 129079 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": 69960, "vin": [ { "gen": { "height": 69950 } } ], "vout": [ { "amount": 359937765421, "target": { "key": "fd8bce12be6c0edae40a626bf293a1df2a91dd6fc02453d214ffcd5984574d1a" } } ], "extra": [ 1, 19, 69, 123, 59, 67, 199, 53, 252, 233, 234, 22, 160, 111, 190, 253, 228, 65, 100, 132, 101, 239, 99, 43, 143, 241, 176, 172, 211, 185, 164, 93, 35, 2, 17, 0, 0, 0, 3, 3, 211, 109, 17, 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