Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0e2604e04f0c0e560487c9a4270a136d326d8b9195a2230cc24366d5bfcdd8

Tx prefix hash: b304dbf560a7bd7c68eaafbf1a88873c82ca5e79a5db06b11a8b95ca83b8ccaf
Tx public key: ca8a1a83238f204cac76690bf173c963f459ff9c5bd7773ae883f25f4f82d0a9
Timestamp: 1578824669 Timestamp [UCT]: 2020-01-12 10:24:29 Age [y:d:h:m:s]: 05:294:02:10:55
Block: 43873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1358060 RingCT/type: yes/0
Extra: 01ca8a1a83238f204cac76690bf173c963f459ff9c5bd7773ae883f25f4f82d0a9021100000046b221b3d1000000000000000000

1 output(s) for total of 439.168700480000 dcy

stealth address amount amount idx
00: 547eed445e12b2d87b38d1c4359bb6d2e5f8cf432e1edb6dcb04aee3a191e2e1 439.168700480000 79615 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": 43883, "vin": [ { "gen": { "height": 43873 } } ], "vout": [ { "amount": 439168700480, "target": { "key": "547eed445e12b2d87b38d1c4359bb6d2e5f8cf432e1edb6dcb04aee3a191e2e1" } } ], "extra": [ 1, 202, 138, 26, 131, 35, 143, 32, 76, 172, 118, 105, 11, 241, 115, 201, 99, 244, 89, 255, 156, 91, 215, 119, 58, 232, 131, 242, 95, 79, 130, 208, 169, 2, 17, 0, 0, 0, 70, 178, 33, 179, 209, 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